# CVE-2026-32703: OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy

> Attackers with repository push access can inject HTML into filenames, causing persistent XSS against project members viewing changesets.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-p423-72h4-fjvp

## What is CVE-2026-32703?

CVE-2026-32703 is a critical cross-site scripting vulnerability in opf openproject, published on 18 Mar 2026. 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 an open-source, web-based project management software. In versions prior to 16.6.9, 17.0.6, 17.1.3, and 17.2.1, the Repositories module did not properly escape filenames displayed from repositories. This allowed an attacker with push access into the repository to create commits with filenames that included HTML code that was injected in the page without proper sanitation. This allowed a persisted XSS attack against all members of this project that accessed the repositories page to display a changeset where the maliciously crafted file was deleted. Versions 16.6.9, 17.0.6, 17.1.3, and 17.2.1 fix the issue.

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

## Which versions are affected by CVE-2026-32703?

It affects 1 product.


Products: Openproject Openproject.

## How do I fix CVE-2026-32703?

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

## Is CVE-2026-32703 being exploited?

There is no known exploitation of CVE-2026-32703 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-22600](https://insights.sbomify.com/CVE-2026-22600/): OpenProject is Vulnerable to Arbitrary File Read via ImageMagick SVG Coder (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32703 and fix it if it is affected.

What it is: CVE-2026-32703 is a critical cross-site scripting vulnerability in opf openproject, published on 18 Mar 2026. 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-2026-32703 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-2026-32703/ (Markdown: https://insights.sbomify.com/CVE-2026-32703/index.md)
```

## Sources

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

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