# CVE-2024-3509: Stored Cross-Site Scripting (XSS) in Management Console of Multiple WSO2 Products via Rich Text Editor

> An attacker with admin access can inject persistent JavaScript into the WSO2 Management Console, enabling data theft or unauthorized actions against other users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-x223-vrgf-8f8m

## What is CVE-2024-3509?

CVE-2024-3509 is a medium-severity cross-site scripting vulnerability in Wso2 Api Manager, published on 2 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in the Management Console of multiple WSO2 products due to insufficient input validation in the Rich Text Editor within the registry section.
To exploit this vulnerability, a malicious actor must have a valid user account with administrative access to the Management Console. If successful, the actor could inject persistent JavaScript payloads, enabling the theft of user data or execution of unauthorized actions on behalf of other users.

While this issue enables persistent client-side script execution, session-related cookies remain protected with the httpOnly flag, preventing session hijacking.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-3509?

It affects 4 products.


Products: Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server as Key Manager.

## How do I fix CVE-2024-3509?

No fix has been published for CVE-2024-3509 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3509 being exploited?

There is no known exploitation of CVE-2024-3509 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2022-29464](https://insights.sbomify.com/CVE-2022-29464/): WSO2 Multiple Products Unrestrictive Upload of File (critical 9.8, exploited in the wild)
- [CVE-2024-6914](https://insights.sbomify.com/CVE-2024-6914/): Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover (critical 9.8)
- [CVE-2020-13226](https://insights.sbomify.com/CVE-2020-13226/): WSO2 API Manager vulnerable to SSRF (critical 9.8)
- [CVE-2025-2905](https://insights.sbomify.com/CVE-2025-2905/): An XML External Entity (XXE) vulnerability in Multiple WSO2 Products (critical 9.1)
- [CVE-2021-42646](https://insights.sbomify.com/CVE-2021-42646/): XML external entity in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3509 and fix it if it is affected.

What it is: CVE-2024-3509 is a medium-severity cross-site scripting vulnerability in Wso2 Api Manager, published on 2 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-3509 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3509/ (Markdown: https://insights.sbomify.com/CVE-2024-3509/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3509
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3509
- OSV: https://osv.dev/vulnerability/CVE-2024-3509

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3509/
Summaries are generated and may contain mistakes; the official description above is the record.