CVE-2025-5770
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA reflected cross-site scripting (XSS) vulnerability exists in the authentication endpoints of multiple WSO2 products due to a lack of output encoding. A malicious actor can inject arbitrary JavaScript payloads into the authentication endpoint, which are reflected back in the response, enabling browser-based attacks. Exploitation may result in redirection to malicious websites, UI manipulation, or unauthorized data access from the victim’s browser. However, session-related cookies are protected with the httpOnly flag, which mitigates session hijacking via this vector.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA reflected cross-site scripting (XSS) vulnerability in WSO2 authentication endpoints allows injection of arbitrary JavaScript payloads via unsanitized user input that gets reflected in the HTTP response, enabling browser-based attacks such as malicious redirection, UI manipulation, and unauthorized data access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.5.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0= 6.0.0= 6.1.0= 7.0.0= 7.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 product and versionCheck the product startup banner or banner.properties file in the installation directory. Alternatively, access the /carbon/admin/login.jsp endpoint (for IS) or /publisher/endpoint (for API Manager) and view the page source or response headers for version information.Affected if The installed version matches 4.2.0, 4.3.0, 4.4.0, or 4.5.0 for API Manager/API Control Plane, or 6.0.0, 6.1.0, 7.0.0, or 7.1.0 for Identity Server.
-
Confirm authentication endpoints are accessibleVerify that the WSO2 authentication endpoints (such as /authenticationendpoint/login.do, /oauth2/authorize, or /commonauth) are reachable over the network and respond to HTTP requests.Affected if The authentication endpoints are exposed and accepting requests.
-
Identify reflected parameters in authentication flowsSubmit a test request to the login endpoint with a benign test string (such as 'TESTINPUT123') in common parameters like 'redirect_uri', 'sp', or 'username' and observe whether this value appears verbatim in the HTTP response body without encoding.Affected if User-supplied input is reflected in the response without encoding or sanitization.
-
Review HTTP response headers and body for XSS vectorsCapture the HTTP response from authentication endpoints using a browser developer tool or proxy (such as Burp Suite or OWASP ZAP) and examine if any parameter values from the request are included in the response HTML without proper output encoding.Affected if The response contains unsanitized user input within HTML context (script tags, event handlers, or HTML attributes).
A user is affected if they run any of the listed WSO2 product versions and their authentication endpoints reflect user input without encoding in HTTP responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement output encoding on all user-supplied input in authentication endpoints and validate/sanitize parameters before reflecting them in HTTP responses.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5770 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data