Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 8 months later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-14561, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Critical9.0CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
NVDNVD · Deferred3.1Critical9.0CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
EPSS (exploitation in 30 days)
0.41% · top 64% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.0.

Affected products

  • WSO2 · WSO2 API Manager

    • affected 4.1.0 – < 4.1.0.242
    • affected 4.2.0 – < 4.2.0.182
    • affected 4.3.0 – < 4.3.0.93
    • affected 4.4.0 – < 4.4.0.57
    • affected 4.5.0 – < 4.5.0.41
    • affected 4.6.0 – < 4.6.0.6
  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.42
    • affected 4.6.0 – < 4.6.0.7
  • WSO2 · WSO2 Traffic Manager

    • affected 4.5.0 – < 4.5.0.40
    • affected 4.6.0 – < 4.6.0.6
  • WSO2 · WSO2 Universal Gateway

    • affected 4.5.0 – < 4.5.0.40
    • affected 4.6.0 – < 4.6.0.6
  • WSO2 · WSO2 Carbon API Management Implementation

    • affected 9.20.74 – < 9.20.74.388
    • affected 9.28.116 – < 9.28.116.395
    • affected 9.29.120 – < 9.29.120.213
    • affected 9.30.67 – < 9.30.67.135
    • affected 9.31.86 – < 9.31.86.108
    • affected 9.32.147 – < 9.32.147.5
    • unaffected 9.32.160 – ≤ *
  • WSO2 · WSO2 Carbon API Manager Rest API Utility

    • affected 9.20.74 – < 9.20.74.388
    • affected 9.28.116 – < 9.28.116.395
    • affected 9.29.120 – < 9.29.120.213
    • affected 9.30.67 – < 9.30.67.135
    • affected 9.31.86 – < 9.31.86.108
    • affected 9.32.147 – < 9.32.147.5
    • unaffected 9.32.160 – ≤ *

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4918/#solution

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-14561 badge
[![CVE-2025-14561](https://cveledger.app/badge/CVE-2025-14561.svg)](https://cveledger.app/cve/CVE-2025-14561)

Record last updated .