# CVE-2025-31500: Cross-site scripting in RT

> Attackers can inject JavaScript into Asset names in Request Tracker, potentially executing code or hijacking user sessions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2025
- **Updated:** 28 May 2025
- **Also known as:** DEBIAN-CVE-2025-31500, GHSA-76w2-jhhw-cjjj, UBUNTU-CVE-2025-31500

## What is CVE-2025-31500?

CVE-2025-31500 is a high-severity cross-site scripting vulnerability in bestpractical RT, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Best Practical RT (Request Tracker) 5.0 through 5.0.7 allows XSS via JavaScript injection in an Asset name.

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

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

It affects 1 product.


Products: Bestpractical Request Tracker.

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

Upgrade to a fixed version.

## Is CVE-2025-31500 being exploited?

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

## Other vulnerabilities in bestpractical RT

- [CVE-2026-44231](https://insights.sbomify.com/CVE-2026-44231/): RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint (critical 9.1)
- [CVE-2017-5943](https://insights.sbomify.com/CVE-2017-5943/): Information disclosure in n/a (high 8.8)
- [CVE-2017-5944](https://insights.sbomify.com/CVE-2017-5944/): Code injection in n/a (high 8.8)
- [CVE-2023-41259](https://insights.sbomify.com/CVE-2023-41259/): Information disclosure in n/a (high 7.5)
- [CVE-2023-41260](https://insights.sbomify.com/CVE-2023-41260/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-31500 is a high-severity cross-site scripting vulnerability in bestpractical RT, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31500 in the wild and no public exploit code.

Affected product: bestpractical RT. 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-31500/ (Markdown: https://insights.sbomify.com/CVE-2025-31500/index.md)
```

## Sources

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

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