Skip to main content
VulnerabilityPublished

CVE-2025-10611: WSO2 API Manager · Incorrect Authorization

Affects WSO2 API ManagerSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.wso2/carbon-apimgtpkg:maven/org.wso2/carbon-apimgtOther threatsAffected
  • =2.1.0
  • =2.2.0
  • =2.5.0
  • =2.6.0
  • =3.0.0
  • =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
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate application of vendor patches or updates once released is the most effective mitigation. Monitor WSO2 advisories for official fixes. 2. If patches are not yet available, restrict network access to the WSO2 API Manager administrative interfaces using firewalls or network segmentation to limit exposure to trusted internal IPs only. 3. Implement Web Application Firewalls (WAFs) with rules to detect and block unauthorized REST API calls targeting administrative endpoints. 4. Enable detailed logging and monitoring of API management activities to detect anomalous or unauthorized access attempts promptly. 5. Conduct a thorough review of API Manager configurations and remove or disable any unnecessary administrative APIs or services. 6. Employ strong identity and access management controls around API management infrastructure, including multi-factor authentication for administrators. 7. Regularly audit API usage and access patterns to identify potential abuse. 8. Prepare incident response plans specifically addressing API management compromise scenarios. These steps go beyond generic advice by focusing on network-level controls, monitoring, and configuration hardening tailored to WSO2 API Manager environments.

Description

Due to an insufficient access control implementation in multiple WSO2 Products, authentication and authorization checks for certain REST APIs can be bypassed, allowing them to be invoked without proper validation. Successful exploitation of this vulnerability could lead to a malicious actor gaining administrative access and performing unauthenticated and unauthorized administrative operations.

References

Community reviews

Loading reviews…