CVE-2025-8325: WSO2 API Control Plane · Assigning Permissions Instead of Checking Them
Affects WSO2 API Control PlaneSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.5.0.18 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.5.0.18, 4.5.0.17, 4.4.0.33 +14
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WSO2WSO2 API Control Plane | Affected
| Fixed in
|
| WSO2WSO2 Universal Gateway | Affected
| Fixed in
|
| WSO2WSO2 Traffic Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict user accounts to trusted personnel only and monitor for unusual API activity. Avoid exposing the vulnerable API Control Plane to untrusted networks. Follow vendor communications closely for updates on patches or official mitigations.
Description
CVE-2025-8325 is a medium severity vulnerability in WSO2 API Control Plane version 4.5.0 where role-based access controls are improperly enforced. Users assigned the 'Internal/Everyone' role can invoke certain Gateway and Internal Service APIs without proper permission checks. This allows any authenticated user to perform sensitive operations on the Gateway REST API regardless of their actual privileges, potentially leading to unintended or unauthorized actions in production environments.