# CVE-2025-14561: Access Control Bypass via Publisher REST APIs in Multiple WSO2 Products Allows Cross-Tenant Operations

> Privileged users in multi-tenant WSO2 deployments can bypass tenant isolation to modify API metadata in other tenants.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-78r2-rh3v-h2fx

## What is CVE-2025-14561?

CVE-2025-14561 is a critical missing authorization vulnerability in WSO2 API Control Plane, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In multi-tenant deployments, the Publisher REST APIs fail to enforce tenant isolation correctly. This allows a user in one tenant, possessing sufficient privileges to invoke these APIs, to perform operations that impact other tenants.

The vulnerability allows a privileged user to perform publisher operations such as exposing or modifying API Metadata in another tenant environment. This impact is only realized in multi-tenant deployments.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-14561 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14561 is a critical missing authorization vulnerability in WSO2 API Control Plane, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14561 in the wild and no public exploit code.

Affected product: WSO2 API Control Plane. 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-14561/ (Markdown: https://insights.sbomify.com/CVE-2025-14561/index.md)
```

## Sources

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

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