Quick answers
- Is CVE-2025-11969 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-11969 being exploited in the wild.
- How severe is CVE-2025-11969?
- Critical severity, with a CVSS score of 9.4, published 2 November 2026.
- Which products and versions are affected?
- Wso2 API Control Plane 4.5.0; Wso2 API Manager 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0; Wso2 Identity Server as Key Manager 5.10.0; Wso2 Open Banking AM 2.0.0; and 3 more.
- Is there a fix for CVE-2025-11969?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-11969 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2025-11969?
- Check whether you run Wso2 API Control Plane, Wso2 API Manager, Wso2 Identity Server as Key Manager or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The System REST APIs in WSO2 products fail to properly validate user privilege levels before allowing access to administrative operations, resulting in broken access control (CWE-284). An unauthenticated or low-privileged network attacker can invoke administrative functions via REST API calls without proper authorization. APIs exposed through the API Manager's API Gateway are not affected.
Affected products
- WSO2 API Control Plane 4.5.0
- WSO2 API Manager 3.1.0, 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0
- WSO2 Identity Server as Key Manager 5.10.0
- WSO2 Open Banking AM 2.0.0
- WSO2 Open Banking IAM 2.0.0
- WSO2 Traffic Manager 4.5.0
- WSO2 Universal Gateway 4.5.0
Timeline
- 2026-01-26: disclosed