Administrative token generation via unsecured DCR methods
Published Oct 16, 2025 · Updated Oct 17, 2025
Missing access control in WSO2 API Manager and API Control Plane affected releases allows remote attackers to obtain elevated tokens. The default method-context configuration omits secure GET, PUT, and DELETE rules for the keymanager-operations DCR registration route, so untrusted requests reach privileged client-management operations. No authentication or user interaction is required; a generated token grants administrative access and enables unauthorized operations.
Summary
What happened
Missing access control in WSO2 API Manager and API Control Plane affected releases allows remote attackers to obtain elevated tokens. The default method-context configuration omits secure GET, PUT, and DELETE rules for the keymanager-operations DCR registration route, so untrusted requests reach privileged client-management operations. No authentication or user interaction is required; a generated token grants administrative access and enables unauthorized operations.
The record
- CVE
- CVE-2025-9152
- Published
- Oct 16, 2025
- Updated
- Oct 17, 2025
- Vendor
- WSO2
- Product
- WSO2 API Control Plane
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.5.0 <4.5.0.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo