Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.0.347, 3.2.0.450, 3.2.1.70, 4.0.0.370, 4.1.0.233, and 27 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.1.0.347, 3.2.0.450, 3.2.1.70, 4.0.0.370, 4.1.0.233, or one of 27 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 3.1.0.347, 3.2.0.450, 3.2.1.70, 4.0.0.370, 4.1.0.233, and 27 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Multiple WSO2 products that expose System REST APIs are affected, and the flaw lets users with lower-privilege roles perform administrative actions they should not be allowed to run. This could allow an attacker to carry out unauthorized administrative operations on the affected product, though APIs exposed through the WSO2 API Manager's API Gateway are not impacted.
Read the original description
The System REST APIs do not correctly enforce access control mechanisms, allowing users with lower privilege roles to execute administrative actions that should be restricted. This weakness permits unauthorized operations on the affected product. Successful exploitation could enable a malicious actor to perform unauthorized administrative operations, including executing administrative functions. APIs exposed through the WSO2 API Manager's API Gateway are not affected by this vulnerability.
What to do
Upgrade to a fixed version: 3.1.0.347, 3.2.0.450, 3.2.1.70, 4.0.0.370, 4.1.0.233, or one of 27 more.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
From 3.1.0 · fixed in 3.1.0.347; From 3.2.0 · fixed in 3.2.0.450; From 3.2.1 · fixed in 3.2.1.70; From 4.0.0 · fixed in 4.0.0.370; From 4.1.0 · fixed in 4.1.0.233; From 4.2.0 · fixed in 4.2.0.173; From 4.3.0 · fixed in 4.3.0.85; From 4.4.0 · fixed in 4.4.0.49; From 4.5.0 · fixed in 4.5.0.32
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.367
- WSO2 WSO2 Open Banking AM
From 2.0.0 · fixed in 2.0.0.396
- WSO2 WSO2 Open Banking IAM
From 2.0.0 · fixed in 2.0.0.416
- WSO2 WSO2 API Control Plane
From 4.5.0 · fixed in 4.5.0.33
- WSO2 WSO2 Universal Gateway
From 4.5.0 · fixed in 4.5.0.31
- WSO2 WSO2 Traffic Manager
From 4.5.0 · fixed in 4.5.0.31
- org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.util
From 6.6.163 · fixed in 6.6.163.159; From 6.6.163 · fixed in 6.6.163.160; From 6.7.206 · fixed in 6.7.206.574; From 6.7.206 · fixed in 6.7.206.576; From 6.7.210 · fixed in 6.7.210.69; From 6.7.210 · fixed in 6.7.210.71; From 9.0.174 · fixed in 9.0.174.536; From 9.20.74 · fixed in 9.20.74.384; From 9.20.74 · fixed in 9.20.74.385; From 9.28.116 · fixed in 9.28.116.380; From 9.29.120 · fixed in 9.29.120.202; From 9.30.67 · fixed in 9.30.67.125; From 9.31.86 · fixed in 9.31.86.90
- org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.common
From 9.0.174 · fixed in 9.0.174.538; From 9.20.74 · fixed in 9.20.74.385; From 9.28.116 · fixed in 9.28.116.382; From 9.29.120 · fixed in 9.29.120.204; From 9.30.67 · fixed in 9.30.67.126; From 9.31.86 · fixed in 9.31.86.91
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-11969
What does this mean?
Some WSO2 system REST APIs do not properly check who is calling them, so a caller without the right access can carry out unauthorized operations, including administrative actions, on the affected product.Source: security.docs.wso2.com
Am I affected, and how do I check?
The facts list many WSO2 products and version ranges, including WSO2 API Manager from 3.1.0 up to 4.5.0 and several Identity Server, Open Banking, API Control Plane, Universal Gateway, Traffic Manager, and Carbon REST API component builds, each with a listed fixed build. To check a deployment, compare the installed product version and build number against the listed fixed builds for that product.Source: security.docs.wso2.com
What should I do about it?
Upgrade each affected WSO2 product to the fixed build listed for its version line, such as 4.5.0.33 or later for API Control Plane, 4.5.0.31 or later for Universal Gateway and Traffic Manager, and 3.1.0.347 or later for API Manager 3.1.0.Source: security.docs.wso2.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data