How severe is GHSA-cmjc-qp7j-xgwr?

GHSA-cmjc-qp7j-xgwr has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cmjc-qp7j-xgwr?

GHSA-cmjc-qp7j-xgwr affects the following packages: org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api (Maven), org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1 (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cmjc-qp7j-xgwr?

Update org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api to 9.31.117 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmjc-qp7j-xgwr is resolved across your whole dependency graph.

How do I detect GHSA-cmjc-qp7j-xgwr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-cmjc-qp7j-xgwr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cmjc-qp7j-xgwr?

O3 pinpoints whether GHSA-cmjc-qp7j-xgwr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-cmjc-qp7j-xgwr actively exploited in the wild?

No public exploit code has been indexed for GHSA-cmjc-qp7j-xgwr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cmjc-qp7j-xgwr?

GHSA-cmjc-qp7j-xgwr has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-cmjc-qp7j-xgwr published, and has it been updated?

GHSA-cmjc-qp7j-xgwr was published on September 23, 2025 and was last updated on September 27, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-cmjc-qp7j-xgwr

MEDIUM

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

Also known asCVE-2025-4760

Published

Sep 23, 2025

Updated

Sep 27, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk7th percentile+0.15%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api☕org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api`	all versions	9.31.117
☕Maven	`org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1`	all versions	9.31.117

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api to 9.31.117 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cmjc-qp7j-xgwr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-cmjc-qp7j-xgwr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-cmjc-qp7j-xgwr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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` s

O3 Security · Impact-Aware SCA

Is GHSA-cmjc-qp7j-xgwr in your dependencies?

O3 detects GHSA-cmjc-qp7j-xgwr across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works