Skip to content
Fencer Vulns
critical 9.0

CVE-2025-14561 json

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

published 2026-08-06 3 mo ago modified 2026-09-29 41 d ago also EUVD-2025-210647

cvss
9.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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.

Patch / fix

  • WSO2 WSO2 API Manager 4.1.0.242, 4.2.0.182, 4.3.0.93, 4.4.0.57, 4.5.0.41, 4.6.0.6
  • WSO2 WSO2 API Control Plane 4.5.0.42, 4.6.0.7
  • WSO2 WSO2 Traffic Manager 4.5.0.40, 4.6.0.6
  • WSO2 WSO2 Universal Gateway 4.5.0.40, 4.6.0.6
  • WSO2 WSO2 Carbon API Management Implementation 9.20.74.388, 9.28.116.395, 9.29.120.213, 9.30.67.135, 9.31.86.108, 9.32.147.5, 9.32.160
  • WSO2 WSO2 Carbon API Manager Rest API Utility 9.20.74.388, 9.28.116.395, 9.29.120.213, 9.30.67.135, 9.31.86.108, 9.32.147.5, 9.32.160

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
3 mo ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.0 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L

Affected products

  • WSO2 WSO2 API Manager
  • WSO2 WSO2 API Control Plane
  • WSO2 WSO2 Traffic Manager
  • WSO2 WSO2 Universal Gateway
  • WSO2 WSO2 Carbon API Management Implementation
  • WSO2 WSO2 Carbon API Manager Rest API Utility

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.