# CVE-2025-24892: OpenProject stored HTML injection vulnerability

> Attackers can inject malicious HTML scripts into group names, leading to stored XSS attacks against other users in OpenProject.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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:** 10 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-mg4q-ghvh-cm2j

## What is CVE-2025-24892?

CVE-2025-24892 is a low-severity cross-site scripting vulnerability in opf openproject, published on 10 Feb 2025. 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 open-source, web-based project management software. In versions prior to 15.2.1, the application fails to properly sanitize user input before displaying it in the Group Management section. Groups created with HTML script tags are not properly escaped before rendering them in a project. The issue has been resolved in OpenProject version 15.2.1. Those who are unable to upgrade may apply the patch manually.

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

## Which versions are affected by CVE-2025-24892?

It affects 1 product.


Products: Openproject Openproject.

## How do I fix CVE-2025-24892?

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

## Is CVE-2025-24892 being exploited?

There is no known exploitation of CVE-2025-24892 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-2025-24892 and fix it if it is affected.

What it is: CVE-2025-24892 is a low-severity cross-site scripting vulnerability in opf openproject, published on 10 Feb 2025. 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-2025-24892 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-2025-24892/ (Markdown: https://insights.sbomify.com/CVE-2025-24892/index.md)
```

## Sources

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

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