Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege account (Internal/Everyone)
-
ExploitInvoke restricted Gateway/Internal Service REST API
-
ExecutionBypass role-based access control checks
-
ImpactPerform unauthorized sensitive operations
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Permission preservation
|
| Exploitation Conditions | Attacker must hold a valid user account on the target deployment, but the abused 'Internal/Everyone' role is assigned to every authenticated user by default, so in practice any account suffices (PR:L, AC:L, no user interaction). The affected surface is the Gateway REST API, plus Internal Service APIs specifically in WSO2 APIM 3.x versions. Limiting factors: exploitation is authenticated-only (no anonymous/unauthenticated path), so exposure depends on who can obtain accounts - internet-facing self-service or broad-tenant deployments are most at risk, while deployments with tightly controlled account provisioning are far less exposed. Affected products span WSO2 API Manager (3.2.x-4.5.x), Universal Gateway, Traffic Manager, API Control Plane, and the Carbon API Management Implementation / REST API Utility components below the fixed patch levels. |
| Impact | Conflicting severity signals: the vendor-supplied CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) rates this 8.8 HIGH with full C:H/I:H/A:H impact, yet nearly every other signal points to low real-world urgency. EPSS is only 0.03% (10th percentile), there is no CISA KEV listing (SSVC Exploitation: none), the issue is not Automatable (no), and CISA's SSVC rates Technical Impact as only 'partial' - directly contradicting the CVSS all-High impact metrics, which should be verified against vendor scoping. Exploitation requires a valid, authenticated account (PR:L), so this is not a remote-unauthenticated internet threat; however the aggravating factor is that the abusable 'Internal/Everyone' role is granted to EVERY authenticated user by default, so any legitimate low-privilege user becomes an attacker. Net: a genuine broken-access-control defect worth patching on a normal cycle, but currently a high-CVSS / low-real-risk item rather than an emergency - no public exploit identified at time of analysis and no evidence of active exploitation. |
| Exploit ScenarioDerived | A low-privilege user who holds only the default 'Internal/Everyone' role - automatically assigned to all accounts - authenticates to a WSO2 API Manager deployment and directly invokes Gateway REST API (and in 3.x, Internal Service API) endpoints that should be restricted to administrators. Because role-based checks are not enforced, the user performs sensitive gateway operations and can disclose internal service information regardless of their assigned privileges. No public exploit code is identified at time of analysis, and the low complexity (AC:L) means a valid account is the only real prerequisite. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 14, 2026
Missing role-based authorization on WSO2 API Manager's Gateway REST API lets any authenticated user invoke privileged Gateway operations, because the 'Internal/Everyone' role that satisfies these checks is granted to every account by default; in WSO2 APIM 3.x the same flaw also exposes Internal Service APIs. Affected deployments span WSO2 API Manager 3.2.0 through 4.5.0 as well as Universal Gateway, Traffic Manager, API Control Plane and the associated Carbon API Management Implementation / REST API Utility components below their fixed patch levels, and exploitation requires only a valid low-privilege account (CVSS 3.1 AV:N/AC:L/PR:L/UI:N, assessed impact on confidentiality and integrity only) - no anonymous path exists. No public exploit code has been identified at time of analysis, EPSS is 0.03% (10th percentile), CISA SSVC records Exploitation: none and Automatable: no, so this is best treated as a high-privilege-bypass risk concentrated in internet-facing or self-service-signup API portals rather than an imminent mass-exploitation threat.
Earlier versions of this analysis (1)
Role-based access control bypass in WSO2 API Manager 3.x allows authenticated users with the 'Internal/Everyone' role to invoke Gateway and Internal Service APIs without proper permission enforcement, enabling unauthorized operations on sensitive REST API endpoints. The vulnerability affects multiple WSO2 products including API Control Plane, Universal Gateway, and Traffic Manager. CVSS 6.3 (network-accessible, low complexity, requires valid user credentials) indicates moderate severity with clear lateral privilege escalation potential in multi-tenant environments.
RemediationAI
Vendor-released patch: apply the WSO2 public security updates at or above the fixed levels for each component - WSO2 API Manager 3.2.0.435, 3.2.1.55, 4.0.0.355, 4.1.0.219, 4.2.0.157, 4.3.0.70, 4.4.0.33 and 4.5.0.17, Universal Gateway 4.5.0.17, Traffic Manager 4.5.0.17, API Control Plane 4.5.0.18, and the corresponding Carbon API Management Implementation / REST API Utility update levels (6.7.206.563, 6.7.210.55, 9.0.174.513, 9.20.74.375, 9.28.116.352, 9.29.120.177, 9.30.67.100, 9.31.86.58) as described in WSO2-2025-4401. Where patching cannot be applied immediately, the highest-value compensating control is to remove the default grant of the 'Internal/Everyone' role and explicitly map the affected Gateway and Internal Service API operations to narrowly scoped administrative roles - with the trade-off that out-of-the-box Gateway functionality, publisher workflows and internal service calls may break until role mappings are tuned and tested. In parallel, restrict network reachability of the Gateway REST API and internal service endpoints to trusted management networks or loopback rather than exposing them alongside the public API data plane, and disable or tightly gate self-service tenant/user registration so that the pool of accounts capable of triggering the bypass is minimized; both measures reduce the attack surface but add operational friction for legitimate administrative traffic and CI/CD automation. Because exploitation is authenticated-only, audit and aggressively re-provision low-privilege, tenant and service accounts on vulnerable deployments, rotate any credentials that may have been used against the Gateway REST API, and review Gateway audit logs for privileged invocations originating from non-administrative principals; note that logging visibility for these calls may be incomplete prior to patching, so absence of findings is not proof of safety.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 6 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is an authorization design defect in the WSO2 API Manager Gateway request-handling stack, classified as CWE-281 (Improper Preservation of Permissions) and functionally a broken access control / missing authorization check: the Gateway REST API and, in APIM 3.x, Internal Service APIs validate the caller against the built-in 'Internal/Everyone' role instead of enforcing the specific administrative or publisher role required by the invoked operation. Because that role is assigned by default to all authenticated principals, the permission boundary collapses for every account. The CPE data confirms the flaw is distributed across the API Manager product line and its internal runtime components - wso2:wso2_api_manager, wso2_universal_gateway, wso2_traffic_manager, wso2_api_control_plane, wso2_carbon_api_management_implementation and wso2_carbon_api_manager_rest_api_utility - meaning the vulnerable Gateway logic is shared across the 3.x, 4.x and 4.5.x release trains and across the Carbon OSGi bundles that implement the management and REST API layers. Successful abuse occurs entirely over the network at the REST/HTTP layer and is non-atomic, single-step, and requires no user interaction, but it is gated on authentication: the attacker must already hold a working credential.
Know when Wso2 Api Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Any authenticated user holds the exploitable default role so PR:L and AC:L; broken access to gateway admin APIs yields confidentiality and integrity impact, but no clear availability destruction (A:N).
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionNVD
The software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal Service APIs, potentially exposing them in WSO2 APIM 3.x versions.
A malicious actor with a valid user account on a vulnerable deployment can perform sensitive operations against the Gateway REST API regardless of their actual roles or privileges. This could lead to unintended behavior or misuse, particularly in production environments.
Executive ViewAI
WSO2 API Manager (versions 3.2.0 through 4.5.0) and its associated Universal Gateway, Traffic Manager, API Control Plane and Carbon API Management components contain a role-based authorization flaw that allows any holder of a valid low-privilege account to reach privileged Gateway operations - and, in 3.x deployments, Internal Service APIs - because the default 'Internal/Everyone' role satisfies those checks for every account. Any organization running these products, particularly with self-service signup or internet-facing Gateway endpoints, effectively grants every registered user administrative-level API management capability, undermining confidentiality and integrity of API configurations and traffic policies. Leadership should treat this as a high-privilege-bypass exposure requiring urgent patching and, in the interim, restriction of who can obtain accounts on these platforms.
Apply vendor patch. Until patching is complete, restrict the Gateway REST API to trusted networks, disable self-service signup and unnecessary accounts, and review role assignments to ensure privileged Gateway operations are not reachable by default-everyone roles.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Wso2 Api Manager
View allAuthentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,
Server-side request forgery in WSO2 API Manager lets unauthenticated remote attackers coerce the gateway into making ser
Privilege escalation in WSO2 API Manager and related Carbon-based products allows a low-privileged user, using a validly
Authentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM,
Persistent denial of service in multiple WSO2 products - including WSO2 API Manager, WSO2 Universal Gateway, WSO2 Traffi
OS command injection (CWE-78) in WSO2's shared Carbon Console administrative interface allows an authenticated administr
Server-side request forgery in WSO2 API Manager and related WSO2 products lets a remote attacker direct the server to ar
Predictable HMAC shared secrets generated by the API Publisher component of WSO2 API Manager allow a sophisticated attac
HTTP response header injection in WSO2 API Manager and its companion WSO2 gateway components (Universal Gateway, Traffic
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the
WSO2 Carbon OAuth, as shipped in WSO2 Identity Server, API Manager, and related WSO2 products, can leave session-bound t
Reflected cross-site scripting across at least eight WSO2 platform products - including Identity Server, API Manager, AP
EUVD-2025-209759
GHSA-xh36-jjpq-3cmr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB