CVE-2025-9152
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn improper privilege management vulnerability exists in WSO2 API Manager due to missing authentication and authorization checks in the keymanager-operations Dynamic Client Registration (DCR) endpoint. A malicious user can exploit this flaw to generate access tokens with elevated privileges, potentially leading to administrative access and the ability to perform unauthorized operations.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper privilege management vulnerability in WSO2 API Manager's keymanager-operations Dynamic Client Registration endpoint allows unauthenticated or improperly authorized users to register OAuth clients and obtain access tokens with elevated privileges, potentially achieving administrative access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.5.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 API Manager versionCheck the product version by reviewing the release.info file in the installation directory, the carbon.xml configuration file, or the runtime version displayed in the WSO2 Admin Console dashboard under the 'About' section.Affected if The installed version matches 3.2.0, 3.2.1, 4.0.0, 4.1.0, 4.2.0, 4.3.0, 4.4.0, or 4.5.0 (for API Manager) or 4.5.0 (for API Control Plane).
-
Verify Dynamic Client Registration endpoint exposureInspect the deployment.yaml or api-manager.xml configuration files to confirm whether the /keymanager-operations/dcr endpoint is enabled and accessible. This is typically found under the OAuthConfigurations section or DynamicClientRegistration settings.Affected if The DCR endpoint is enabled and reachable without proper network restrictions or authentication barriers.
-
Review DCR endpoint authorization configurationExamine the identity provider configuration and the API authorization settings for the Dynamic Client Registration endpoint in the WSO2 Management Console. Check if role-based access controls are properly enforced for client registration requests.Affected if The DCR endpoint allows client registration without requiring administrator-level authentication or proper authorization validation.
-
Audit existing OAuth client registrationsQuery the OIDC table in the WSO2 database or review registered OAuth clients through the Admin Console under Service Providers > List. Look for unexpected clients with grant types like client_credentials or authorization_code that may have elevated permissions.Affected if Unexpected or unauthorized OAuth clients exist with elevated scopes or roles that were not created by legitimate administrators.
You are affected if you run any of the listed WSO2 API Manager or Control Plane versions AND the Dynamic Client Registration endpoint is accessible without proper administrative authorization controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor-supplied patches for CVE-2025-9152 and implement proper authentication and authorization validation on the DCR endpoint to ensure only authorized administrators can register clients with elevated permissions.
WSO2 API Manager 4.6.0 or later stable release
- 1. Backup your current WSO2 API Manager configuration and database
- 2. Download the latest stable release of WSO2 API Manager (4.6.0 or later) from the official WSO2 website
- 3. Review the migration guide for your current version to ensure compatibility
- 4. Stop the running API Manager services
- 5. Install the new version following the WSO2 installation documentation
- 6. Migrate your existing configurations and data using the provided migration client
- 7. Start the upgraded API Manager services
- 8. Verify the keymanager-operations DCR endpoint now requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9152 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data