# CVE-2025-12544: WSO2 API Manager SVG upload stored XSS in Publisher portal

Source: https://junglewise.ai/threats/cve-2025-12544-the-publisher-portal-fails-to-enforce-proper-validation-on  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2025-12544 · Severity: medium · CVSS 4.8 · Published 2026-11-02

WSO2 API Manager is a platform for managing and publishing APIs. A user with Publisher role permissions can upload a malicious SVG file to the portal, injecting JavaScript code that runs in other users' browsers. An attacker can redirect victims to phishing sites, modify page content, or steal browser data, though session cookies are protected against hijacking.

Technologies: [Wso2 API Manager](https://junglewise.ai/threats/technologies/api-manager). Vendors: [Wso2](https://junglewise.ai/threats/vendors/wso2).

## Quick answers

**Is CVE-2025-12544 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-12544 being exploited in the wild.

**How severe is CVE-2025-12544?** Medium severity, with a CVSS score of 4.8, published 2 November 2026.

**Which products and versions are affected?** Wso2 API Manager 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0.

**Is there a fix for CVE-2025-12544?** Yes: fixed in WSO2 API Manager 4.2.0 U2.7, 4.1.0 U2.60, 4.0.0 U2.368, 3.2.1 U2.68, 3.2.0 U2.449. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-12544 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2025-12544?** Check whether you run Wso2 API Manager at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in WSO2 API Manager 4.2.0 U2.7, 4.1.0 U2.60, 4.0.0 U2.368, 3.2.1 U2.68, 3.2.0 U2.449

## Technical details

The Publisher portal fails to validate uploaded SVG files, allowing authenticated users with the Publisher role to upload SVG files containing embedded malicious scripts. The vulnerability is a stored XSS issue triggered when the SVG is rendered by the application in victims' browsers. Requires user interaction (viewing the malicious SVG) and Publisher role authentication, but httpOnly cookie protections prevent session hijacking.

## Affected products

- WSO2 API Manager 4.2.0, 4.1.0, 4.0.0, 3.2.1, 3.2.0

## Timeline

- 2026-06-18: disclosed

## References

- [https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/](https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4500/)

## Related threats

- [WSO2 Identity Server privilege escalation via shared database](https://junglewise.ai/threats/cve-2026-4052-this-issue-only-impacts-deployments-where-wso2-identity-server-is)
- [WSO2 API Manager Admin REST API SQL injection](https://junglewise.ai/threats/cve-2026-2613-the-admin-rest-api-accepts-user-supplied-input-without-adequately)
- [WSO2 products sensitive information disclosure in Event Publisher logs](https://junglewise.ai/threats/cve-2026-18800-when-an-event-publisher-output-adapter-is-configured-with)
- [WSO2 System REST APIs access control bypass](https://junglewise.ai/threats/cve-2025-11969-the-system-rest-apis-do-not-correctly-enforce-access-control)
- [WSO2 username enumeration in external user store authentication](https://junglewise.ai/threats/cve-2024-7478-when-a-wso2-product-is-configured-to-use-an-external-user-store)
