Live › vulnerability › CVE-2025-5769
The authentication endpoint renders user-supplied input without encoding, so an attacker can inject JavaScript that runs in a victim's browser. The attacker can redirect users, alter the displayed page, or read browser data, but session cookies are httpOnly and cannot be stolen this way.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 07:19 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The authentication endpoint does not properly encode user-supplied input before rendering it within the web page. This lack of output encoding allows an attacker to inject malicious JavaScript payloads into the authentication flow, which are then executed by the victim's browser.
By exploiting this vulnerability, an attacker can redirect the user's browser to a malicious website, modify the content of the web page displayed to the user, or exfiltrate information from the browser. However, due to the implementation of the httpOnly flag on session-related sensitive cookies, session hijacking and similar attacks are not possible.
This page as .md · .json · in your agent: get_signal("CVE-2025-5769")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.