Skip to content
Fencer Intel
medium 6.1

CVE-2025-5769 json

Reflected Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Allows Browser Redirection and UI Modification

published 6d ago modified 4h ago also EUVD-2025-211244

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

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.

Patch / fix

  • WSO2 WSO2 API Control Plane 4.5.0.11
  • WSO2 WSO2 API Manager 3.2.0.430, 3.2.1.50, 4.1.0.212, 4.2.0.150, 4.3.0.63, 4.4.0.26, 4.5.0.10
  • WSO2 WSO2 Identity Server 5.10.0.359, 5.11.0.404, 6.0.0.237, 6.1.0.234, 7.0.0.107, 7.1.0.12

Is CVE-2025-5769 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3d ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

  • WSO2 WSO2 API Control Plane
  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Identity Server

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.