CVE-2025-4760

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-4760 has a CVSS score of 4.8 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.31.117); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-4760? CVE-2025-4760 is a medium-severity cross-site scripting (XSS) vulnerability in org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api (maven), affecting versions < 9.31.117. It is fixed in 9.31.117. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-4760? CVE-2025-4760 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-4760?
   • org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api (maven) (versions < 9.31.117)
   • org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1 (maven) (versions < 9.31.117)
4. Is there a fix for CVE-2025-4760? Yes. CVE-2025-4760 is fixed in 9.31.117. Upgrade to this version or later.
5. Is CVE-2025-4760 exploitable, and should I be worried? Whether CVE-2025-4760 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-4760 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-4760?
   • Upgrade org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.api to 9.31.117 or later
   • Upgrade org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1 to 9.31.117 or later