CVE-2025-8325: Improper Access Control via Gateway API in Multiple WSO2 Products Allows Unauthorized Operations
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 6.3, NVD 8.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 11, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-281
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.8
- CNA · WSO2
- 6.3
- 2.5 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api control plane | cpe:2.3:a:wso2:api_control_plane |
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | traffic manager | cpe:2.3:a:wso2:traffic_manager |
| wso2 | universal gateway | cpe:2.3:a:wso2:universal_gateway |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api control plane4.5.0 and later · before 4.5.0.18
- wso2 api manager3.2.0 and later · before 3.2.0.435
- wso2 api manager3.2.1 and later · before 3.2.1.55
- wso2 api manager4.0.0 and later · before 4.0.0.355
- wso2 api manager4.1.0 and later · before 4.1.0.219
- wso2 api manager4.2.0 and later · before 4.2.0.157
- wso2 api manager4.3.0 and later · before 4.3.0.70
- wso2 api manager4.4.0 and later · before 4.4.0.33
- wso2 api manager4.5.0 and later · before 4.5.0.17
- wso2 traffic manager4.5.0 and later · before 4.5.0.17
- wso2 universal gateway4.5.0 and later · before 4.5.0.17
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.18affected
WSO2 WSO2 API Manager
- before 3.2.0unknown
- 3.2.0 and later · before 3.2.0.435affected
- 3.2.1 and later · before 3.2.1.55affected
- 4.0.0 and later · before 4.0.0.355affected
- 4.1.0 and later · before 4.1.0.219affected
- 4.2.0 and later · before 4.2.0.157affected
- 4.3.0 and later · before 4.3.0.70affected
- 4.4.0 and later · before 4.4.0.33affected
- 4.5.0 and later · before 4.5.0.17affected
WSO2 WSO2 Carbon API Management Implementation
- 6.7.206 and later · before 6.7.206.563affected
- 6.7.210 and later · before 6.7.210.55affected
- 9.0.174 and later · before 9.0.174.513affected
- 9.20.74 and later · before 9.20.74.375affected
- 9.28.116 and later · before 9.28.116.352affected
- 9.29.120 and later · before 9.29.120.177affected
- 9.30.67 and later · before 9.30.67.100affected
- 9.31.86 and later · before 9.31.86.58affected
- 9.32.75 and laternot affected
WSO2 WSO2 Carbon API Manager Rest API Utility
- 6.7.206 and later · before 6.7.206.563affected
- 6.7.210 and later · before 6.7.210.55affected
- 9.0.174 and later · before 9.0.174.513affected
- 9.20.74 and later · before 9.20.74.375affected
- 9.28.116 and later · before 9.28.116.352affected
- 9.29.120 and later · before 9.29.120.177affected
- 9.30.67 and later · before 9.30.67.100affected
- 9.31.86 and later · before 9.31.86.58affected
- 9.32.75 and laternot affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.17affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.17affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV77This week
- CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover39Monitor
- CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-13590Feb 19, 2026 · Authenticated arbitrary file upload via a System REST API requiring administrator permission.28Monitor
- ← EarlierCVE-2025-8154May 11, 2026 · HTTP Header Injection via Webhook API in Multiple WSO2 Products Allows Response Header Manipulation30Monitor
- Later →CVE-2026-4249Jul 6, 2026 · Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0209 · May 12, 2026(WSO2 Çoklu Ürün Güvenlik Bildirimi )
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-281 · Improper Preservation of PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.