CVE-2025-10611: Potential Broken Access Control in Multiple WSO2 Products via System REST APIs

21

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.8% (30-day exploitation probability)+8
Technical severity (critical)+10
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.82%

ahead of 56% of scored CVEs · Oct 14, 2026

Affects

WSO2

Api Control Plane and 10 more

CVSS base

9.8

Critical · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Control Plane, WSO2 Api Manager, WSO2 Identity Server…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
WSO2	Api Control Plane	version 4.5.0	Vulnerable	NIST National Vulnerability Database
WSO2	Api Control Plane	≥ 4.5.0 and < 4.5.0.29	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Api Manager	version 2.1.0version 2.2.0version 2.5.0version 2.6.0version 3.0.0version 3.1.0version 3.2.0version 3.2.1 and 6 more version 4.0.0version 4.1.0version 4.2.0version 4.3.0version 4.4.0version 4.5.0	Vulnerable	NIST National Vulnerability Database
WSO2	Api Manager	≥ 2.1.0 and < 2.1.0.42≥ 2.2.0 and < 2.2.0.61≥ 2.5.0 and < 2.5.0.87≥ 2.6.0 and < 2.6.0.148≥ 3.0.0 and < 3.0.0.178≥ 3.1.0 and < 3.1.0.345≥ 3.2.0 and < 3.2.0.446≥ 3.2.1 and < 3.2.1.66 and 6 more ≥ 4.0.0 and < 4.0.0.366≥ 4.1.0 and < 4.1.0.228≥ 4.2.0 and < 4.2.0.169≥ 4.3.0 and < 4.3.0.81≥ 4.4.0 and < 4.4.0.45≥ 4.5.0 and < 4.5.0.28	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Identity Server	version 5.3.0version 5.5.0version 5.6.0version 5.7.0version 5.8.0version 5.9.0version 5.10.0version 5.11.0 and 4 more version 6.0.0version 6.1.0version 7.0.0version 7.1.0	Vulnerable	NIST National Vulnerability Database
WSO2	Identity Server	≥ 5.3.0 and < 5.3.0.39≥ 5.5.0 and < 5.5.0.54≥ 5.6.0 and < 5.6.0.62≥ 5.7.0 and < 5.7.0.128≥ 5.8.0 and < 5.8.0.112≥ 5.9.0 and < 5.9.0.171≥ 5.10.0 and < 5.10.0.375≥ 5.11.0 and < 5.11.0.419 and 4 more ≥ 6.0.0 and < 6.0.0.248≥ 6.1.0 and < 6.1.0.248≥ 7.0.0 and < 7.0.0.124≥ 7.1.0 and < 7.1.0.31	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Identity Server As Key Manager	version 5.3.0version 5.5.0version 5.6.0version 5.7.0version 5.9.0version 5.10.0	Vulnerable	NIST National Vulnerability Database
WSO2	Identity Server As Key Manager	≥ 5.3.0 and < 5.3.0.44≥ 5.5.0 and < 5.5.0.55≥ 5.6.0 and < 5.6.0.77≥ 5.7.0 and < 5.7.0.127≥ 5.9.0 and < 5.9.0.178≥ 5.10.0 and < 5.10.0.365	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Am	version 1.4.0version 1.5.0version 2.0.0	Vulnerable	NIST National Vulnerability Database
WSO2	Open Banking Am	≥ 1.4.0 and < 1.4.0.141≥ 1.5.0 and < 1.5.0.142≥ 2.0.0 and < 2.0.0.394	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Iam	version 2.0.0	Vulnerable	NIST National Vulnerability Database
WSO2	Open Banking Iam	≥ 2.0.0 and < 2.0.0.414	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Open Banking Km	version 1.4.0version 1.5.0	Vulnerable	NIST National Vulnerability Database
WSO2	Open Banking Km	≥ 1.4.0 and < 1.4.0.135≥ 1.5.0 and < 1.5.0.125	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.service	≥ 1.1.1 and < 1.1.1.7≥ 1.1.16 and < 1.1.16.6≥ 1.1.18 and < 1.1.18.7≥ 1.1.20 and < 1.1.20.9≥ 1.1.26 and < 1.1.26.11≥ 1.3.6 and < 1.3.6.11≥ 1.4.0 and < 1.4.0.21≥ 1.4.25 and < 1.4.25.27 and 8 more ≥ 1.4.52 and < 1.4.52.6≥ 1.6.1 and < 1.6.1.12≥ 1.7.1 and < 1.7.1.7≥ 1.8.11 and < 1.8.11.8≥ 1.8.41 and < 1.8.41.4≥ 1.9.4 and < 1.9.4.9≥ 1.9.18 and < 1.9.18.7≥ 1.8 and < 1.8.48	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.valve	≥ 1.1.1 and < 1.1.1.7≥ 1.1.16 and < 1.1.16.6≥ 1.1.18 and < 1.1.18.7≥ 1.1.20 and < 1.1.20.9≥ 1.1.26 and < 1.1.26.11≥ 1.3.6 and < 1.3.6.11≥ 1.4.0 and < 1.4.0.21≥ 1.4.25 and < 1.4.25.27 and 8 more ≥ 1.4.52 and < 1.4.52.6≥ 1.6.1 and < 1.6.1.12≥ 1.7.1 and < 1.7.1.7≥ 1.8.11 and < 1.8.11.8≥ 1.8.41 and < 1.8.41.4≥ 1.9.4 and < 1.9.4.9≥ 1.9.18 and < 1.9.18.7≥ 1.8 and < 1.8.48	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Traffic Manager	version 4.5.0	Vulnerable	NIST National Vulnerability Database
WSO2	Traffic Manager	≥ 4.5.0 and < 4.5.0.27	Vulnerable	CVE Program (cve.org) e CISA ADP
WSO2	Universal Gateway	version 4.5.0	Vulnerable	NIST National Vulnerability Database
WSO2	Universal Gateway	≥ 4.5.0 and < 4.5.0.27	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.8	CVSS 3.1	Critical	3.9	5.9	ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
9.8	CVSS 3.1	Critical	—	—	WSO2 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.82%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Audit administrative actions and access to resources outside each user’s normal pattern.

web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · wso2/wso2 api manager, wso2/wso2 api control plane, wso2/wso2 open banking am, wso2/wso2 open banking iam, wso2/wso2 ide
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 9.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Oct 16, 2025 · WSO2

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

WSO2
every CVE for this vendor

Access control
same class

CWE-863
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2024-8122 Potential brute force vulnerability due to non-expiring SMS OTPs 8d
Medium CVE-2025-5802 Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery Sep 15, 2026
Low CVE-2025-13166 Username Enumeration via SMS OTP Flow in WSO2 Identity Server Allows User Account Discovery Sep 15, 2026
Medium CVE-2026-4103 Cross-Site Scripting via HTML Sanitization in WSO2 Publisher and Developer Portals Allows Malicious Script Execution Sep 14, 2026
Medium CVE-2026-3096 Reverse Tabnabbing via New Tab Navigation in Multiple WSO2 Products Allows Phishing and Credential Theft Sep 10, 2026
High CVE-2025-12737 Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution Sep 3, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-10611 is "Potential Broken Access Control in Multiple WSO2 Products via System REST APIs", rated Critical. It affects Api Control Plane (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 0.82% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.