VulnerabilityPublished 5 Nov 2025

CVE-2025-10853: WSO2 Open Banking IAM · XSS or 'Cross-site Scripting'

Affects WSO2 Open Banking IAMSource CVE Database V5

Not known to be exploited · CVSS 5.2 Medium.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score

5.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.wso2/openbanking-iam`pkg:maven/org.wso2/openbanking-iam`Other threats	Affected =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

Organizations should implement multiple layers of defense to mitigate this vulnerability. First, apply any available patches or updates from WSO2 promptly once released. In the absence of patches, implement strict input validation and output encoding on all parameters processed by the management console to neutralize malicious scripts. Restrict access to the management console to trusted networks and enforce strong authentication and authorization controls. Employ web application firewalls (WAFs) with rules designed to detect and block reflected XSS payloads targeting WSO2 products. Educate administrators and users about the risks of clicking on suspicious links and encourage the use of browser security features such as script blockers or content security policies (CSP) to limit script execution. Regularly audit and monitor management console access logs for unusual activity. Finally, consider network segmentation to isolate the management console from less trusted environments, reducing the attack surface.

Description

CVE-2025-10853 is a reflected cross-site scripting (XSS) vulnerability in the management console of WSO2 Open Banking IAM version 2.0.0. It arises from improper output encoding of user-supplied input, allowing attackers to inject arbitrary JavaScript via manipulated parameters. Exploitation can lead to UI manipulation, redirection to malicious sites, or theft of browser data. Although session cookies are protected with the httpOnly flag, reducing session hijacking risks, the vulnerability still poses confidentiality and integrity concerns. The CVSS score is 5.2 (medium severity), reflecting the need for user interaction and the attack vector being adjacent network. No known exploits are currently in the wild. European organizations using WSO2 Open Banking IAM should prioritize patching and input validation to mitigate risks.

Impact

For European organizations, especially those in the financial sector leveraging WSO2 Open Banking IAM for identity and access management, this vulnerability poses a risk to confidentiality and integrity of user interactions with the management console. While it does not directly compromise availability or allow session hijacking, attackers could manipulate the UI or redirect users to malicious sites, potentially facilitating further attacks such as credential theft or malware delivery. Given the critical role of IAM in securing banking infrastructure, exploitation could undermine trust and compliance with regulations like PSD2 and GDPR. The impact is heightened in environments where management consoles are exposed beyond tightly controlled internal networks. Additionally, attackers could use this vulnerability as a stepping stone for social engineering or lateral movement within networks. The absence of known exploits reduces immediate risk, but the medium severity score and potential for targeted attacks warrant proactive mitigation.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4486/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2025, 20:19 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats