# CVE-2025-8325: Improper Access Control via Gateway API in Multiple WSO2 Products Allows Unauthorized Operations

> Authenticated users with low privileges can bypass access controls to perform unauthorized operations on WSO2 Gateway APIs.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-xh36-jjpq-3cmr

## What is CVE-2025-8325?

CVE-2025-8325 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2025-8325?

It affects 4 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Traffic Manager, Wso2 Universal Gateway.

## How do I fix CVE-2025-8325?

No fix has been published for CVE-2025-8325 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8325 being exploited?

There is no known exploitation of CVE-2025-8325 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8325 and fix it if it is affected.

What it is: CVE-2025-8325 is a medium-severity missing authorization vulnerability in Wso2 Api Manager, published on 11 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8325 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8325/ (Markdown: https://insights.sbomify.com/CVE-2025-8325/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8325
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8325
- OSV: https://osv.dev/vulnerability/CVE-2025-8325

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8325/
Summaries are generated and may contain mistakes; the official description above is the record.