VulnerabilityPublished 6 Aug 2026

CVE-2025-13394: WSO2 Identity Server · Cross-Site Request Forgery (CSRF)

Affects WSO2 Identity ServerSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium · fixed in 7.2.0.3 : update WSO2 Identity Server when convenient.

Data as of 5 Nov 2026, 23:23 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.2.0.3, 7.1.0.41, 7.0.0.133 +104

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-8rr2-f52p-r9q3

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
WSO2WSO2 Identity Server	Affected >=7.2.0 <7.2.0.3	Fixed in 7.2.0.3
WSO2WSO2 Identity Server	Affected >=7.1.0 <7.1.0.41	Fixed in 7.1.0.41
WSO2WSO2 Identity Server	Affected >=7.0.0 <7.0.0.133	Fixed in 7.0.0.133
WSO2WSO2 Identity Server	Affected >=6.1.0 <6.1.0.256	Fixed in 6.1.0.256
WSO2WSO2 Identity Server	Affected >=6.0.0 <6.0.0.255	Fixed in 6.0.0.255
WSO2WSO2 Identity Server	Affected >=5.11.0 <5.11.0.428	Fixed in 5.11.0.428

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

AI-suggested

WSO2 recommends not exposing the Carbon console and related services to the public internet, which effectively mitigates the risk. Organizations should follow this guidance to prevent exploitation.

Description

CVE-2025-13394 is a Cross-Site Request Forgery (CSRF) vulnerability in the Ajax processor of the Carbon console within WSO2 Identity Server. The vulnerability arises because state-changing operations use the HTTP GET method and rely on the SameSite=Lax cookie attribute for CSRF mitigation, which can be bypassed. This allows attackers to trick authenticated users into unknowingly performing unauthorized actions. Exploitation requires the Carbon console and related services to be publicly accessible, which is against WSO2's security recommendations.

Impact

An attacker can perform unauthorized state-changing actions on behalf of authenticated users, potentially leading to data modification, account changes, or loss of user control. The vulnerability does not impact confidentiality but affects integrity and availability due to unauthorized changes and possible service disruption. Exploitation requires user interaction and public exposure of the Carbon console, limiting the attack surface.

Summary

The Ajax processor in the Carbon console of WSO2 Identity Server does not adequately protect state-changing operations from CSRF attacks. It uses HTTP GET requests for these operations and relies on the SameSite=Lax cookie attribute, which permits cookies to be sent with cross-origin top-level navigation GET requests. This design flaw allows attackers to cause authenticated users' browsers to execute unintended state-altering requests without their consent. The vulnerability affects multiple specific versions of WSO2 Identity Server. There is no official remediation or patch currently documented, and the vulnerability is only exploitable if the affected services are exposed to the public internet.

CWE-352Cross-Site Request Forgery (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
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
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (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/2026/WSO2-2025-4800/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Aug 2026, 17:33 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats