Skip to main content
VulnerabilityPublished

CVE-2025-10853: A reflected cross-site scripting (XSS) vulnerability exists in the management console of multiple

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-10853· Medium 5.2

Not known to be exploited · CVSS 5.2 Medium.

Data as of 4 Nov 2026, 18:22 UTC

CVSS 3.1 base score
5.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (WSO2)CVSS 3.15.2
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.wso2/openbanking-iampkg:maven/org.wso2/openbanking-iamOther threatsAffected
  • =2.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should apply best practices for input validation and output encoding in their deployments and consider restricting access to the management console to trusted networks.

Description

CVE-2025-10853 is a reflected cross-site scripting (XSS) vulnerability found in the management console of multiple WSO2 products. It arises from improper output encoding of specific parameters, allowing an attacker to inject arbitrary JavaScript into the response. Exploitation can lead to UI manipulation, redirection to malicious sites, or theft of browser data. The risk of session hijacking is mitigated by the use of the httpOnly flag on session cookies.

References

Community reviews

Loading reviews…