WSO2 carbon-apimgt affected by an authenticated stored cross-site scripting (XSS) vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2025-4760: 0.19% estimated exploitation activity in the next 30 days; percentile 8.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An authenticated stored Cross-Site Scripting (XSS) vulnerability exists in WSO2 API Manager components (carbon-apimgt) due to insufficient validation of user-supplied input during API document upload in the Publisher portal. A user with publisher privileges can upload a crafted API document whose contents are later rendered in the UI for other users, leading to attacker-controlled script execution. Likely outcomes include redirection to malicious sites, unauthorized UI modifications, or exfiltration of data accessible to the browser; session hijacking is mitigated by the use of HttpOnly session cookies. To remediate, update to version 9.31.117 or above.

Published by the source

23 Sep 2025, 15:31 UTC

Last modified by the source

27 Sep 2025, 03:38 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cmjc-qp7j-xgwr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-4760

Advisory: WSO2 carbon-apimgt affected by an authenticated stored cross-site scripting (XSS) vulnerability
IDs: CVE-2025-4760, GHSA-cmjc-qp7j-xgwr
Record: https://patchnext.com/advisories/cve-2025-4760 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1 9.31.117; org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api 9.31.117. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1: affected < 9.31.117; fixed in 9.31.117
- Maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api: affected < 9.31.117; fixed in 9.31.117

## Suggested inspection (read-only)
- Maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1: check the installed version with your package manager.
- Maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1, org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cmjc-qp7j-xgwr (GitHub-reviewed advisory GHSA-cmjc-qp7j-xgwr lists affected ranges: Maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api >=0 =0 <9.31.117)

Commands are suggestions: review each one before running it.