Skip to content
Noroxi
CVE-2025-6670· NVD / CVE Program· CNA WSO2

Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services

A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP GET method for state-changing operations within admin services, specifically in the event processor of the Carbon console. Although the SameSite=Lax cookie attribute is used as a mitigation, it is ineffective in this context because it allows cookies to be sent with cross-origin top-level navigations using GET requests. A malicious actor can exploit this vulnerability by tricking an authenticated user into visiting a crafted link, leading the browser to issue unintended state-changing requests. Successful exploitation could result in unauthorized operations such as data modification, account changes, or other administrative actions. According to WSO2 Secure Production Guidelines, exposure of Carbon console services to untrusted networks is discouraged, which may reduce the impact in properly secured deployments.

HighCVSS 8.8 · v3.1—No exploit No fix recorded
Published
Nov 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
wso2api control plane
wso2api manager
wso2enterprise integrator
wso2identity server
wso2identity server as key manager
wso2open banking am
wso2open banking iam
wso2traffic manager
wso2universal gateway

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api control plane4.5.0
  • wso2 api control plane4.6.0
  • wso2 api manager3.1.0
  • wso2 api manager3.2.0
  • wso2 api manager3.2.1
  • wso2 api manager4.0.0
  • wso2 api manager4.1.0
  • wso2 api manager4.2.0
  • wso2 api manager4.3.0
  • wso2 api manager4.4.0
  • wso2 api manager4.5.0
  • wso2 api manager4.6.0
  • wso2 enterprise integrator6.6.0
  • wso2 identity server5.10.0
  • wso2 identity server5.11.0
  • wso2 identity server6.0.0
  • wso2 identity server6.1.0
  • wso2 identity server7.0.0
  • wso2 identity server7.1.0
  • wso2 identity server7.2.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 org.wso2.carbon:org.wso2.carbon.ui

    • 4.5.3 and later · before 4.5.3.50affected
    • 4.6.0 and later · before 4.6.0.2253affected
    • 4.6.1 and later · before 4.6.1.157affected
    • 4.6.2 and later · before 4.6.2.673affected
    • 4.6.3 and later · before 4.6.3.41affected
    • 4.6.4 and later · before 4.6.4.22affected
    • 4.7.1 and later · before 4.7.1.73affected
    • 4.8.1 and later · before 4.8.1.43affected
    • 4.9.0 and later · before 4.9.0.106affected
    • 4.9.26 and later · before 4.9.26.31affected

  • WSO2 WSO2 API Control Plane

    • 4.5.0 and later · before 4.5.0.36affected
    • 4.6.0 and later · before 4.6.0.1affected

  • WSO2 WSO2 API Manager

    • before 3.1.0unknown
    • 3.1.0 and later · before 3.1.0.349affected
    • 3.2.0 and later · before 3.2.0.453affected
    • 3.2.1 and later · before 3.2.1.73affected
    • 4.0.0 and later · before 4.0.0.373affected
    • 4.1.0 and later · before 4.1.0.236affected
    • 4.2.0 and later · before 4.2.0.176affected
    • 4.3.0 and later · before 4.3.0.88affected
    • 4.4.0 and later · before 4.4.0.52affected
    • 4.5.0 and later · before 4.5.0.35affected

  • WSO2 WSO2 Enterprise Integrator

    • before 6.6.0unknown
    • 6.6.0 and later · before 6.6.0.226affected

  • WSO2 WSO2 Identity Server

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.378affected
    • 5.11.0 and later · before 5.11.0.425affected
    • 6.0.0 and later · before 6.0.0.252affected
    • 6.1.0 and later · before 6.1.0.253affected
    • 7.0.0 and later · before 7.0.0.130affected
    • 7.1.0 and later · before 7.1.0.38affected
    • 7.2.0 and later · before 7.2.0.1affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.369affected

  • WSO2 WSO2 Open Banking AM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.398not affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.418not affected

  • WSO2 WSO2 Traffic Manager

    • 4.5.0 and later · before 4.5.0.34affected
    • 4.6.0 and later · before 4.6.0.1affected

  • WSO2 WSO2 Universal Gateway

    • 4.5.0 and later · before 4.5.0.34affected
    • 4.6.0 and later · before 4.6.0.1affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
    70This week
  • CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover
    39Monitor
  • CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products
    39Monitor
  • CVE-2025-9152Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint
    39Monitor
  • CVE-2025-10611Potential Broken Access Control in Multiple WSO2 Products via System REST APIs
    39Monitor
  • CVE-2025-15039Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-13394261 days apartCross-Site Request Forgery via Ajax Processor Endpoints in Multiple WSO2 Products Enables Unauthorized Actions
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-352 · Cross-Site Request Forgery (CSRF)

CVSS vector

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

nvd-secondary

Root cause

State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

The bug in code

The whole CWE-352 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

Fixed

ts
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records