# CVE-2025-9158: Stored XSS in Request Tracker

> Attackers can execute JavaScript in logged-in users' browsers via crafted emails in Request Tracker, potentially leading to account takeover.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-9158, GHSA-4wp5-pw3x-6v2m, UBUNTU-CVE-2025-9158

## What is CVE-2025-9158?

CVE-2025-9158 is a medium-severity cross-site scripting vulnerability in Best Practical Request Tracker, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Request Tracker software is vulnerable to a Stored XSS vulnerability in calendar invitation parsing feature, which displays invitation data without HTML sanitization. XSS vulnerability allows an attacker to send a specifically crafted e-mail enabling JavaScript code execution by displaying the ticket in the context of the logged-in user. 

This vulnerability affects versions from 5.0.4 through 5.0.8 and from 6.0.0 through 6.0.1.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-9158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9158 and fix it if it is affected.

What it is: CVE-2025-9158 is a medium-severity cross-site scripting vulnerability in Best Practical Request Tracker, published on 24 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9158 in the wild and no public exploit code.

Affected product: Best Practical Request Tracker. 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-9158/ (Markdown: https://insights.sbomify.com/CVE-2025-9158/index.md)
```

## Sources

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

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