# CVE-2024-35224: Stored Cross-Site Scripting (XSS) in OpenProject

> Stored XSS in OpenProject allows attackers with specific permissions to execute scripts, potentially escalating privileges to System Admin.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-h26c-j8wg-frjc

## What is CVE-2024-35224?

CVE-2024-35224 is a high-severity cross-site scripting vulnerability in opf openproject, published on 23 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OpenProject is the leading open source project management software. OpenProject utilizes `tablesorter` inside of the Cost Report feature. This dependency, when misconfigured, can lead to Stored XSS via `{icon}` substitution in table header values. This attack requires the permissions "Edit work packages" as well as "Add attachments". A project admin could attempt to escalate their privileges by sending this XSS to a System Admin. Otherwise, if a full System Admin is required, then this attack is significantly less impactful. By utilizing a ticket's attachment, you can store javascript in the application itself and bypass the application's CSP policy to achieve Stored XSS. This vulnerability has been patched in version(s) 14.1.0, 14.0.2 and 13.4.2.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

It affects 1 product.


Products: Openproject Openproject.

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

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

## Is CVE-2024-35224 being exploited?

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

## Other vulnerabilities in opf openproject

- [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9)
- [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4)
- [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4)
- [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1)
- [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35224 is a high-severity cross-site scripting vulnerability in opf openproject, published on 23 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-35224 in the wild and no public exploit code.

Affected product: opf openproject. 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-35224/ (Markdown: https://insights.sbomify.com/CVE-2024-35224/index.md)
```

## Sources

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

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