CVE-2025-61873 Other in Request Tracker
Low 2.6
Published
Updated
Check this codebase for CVE-2025-61873 and fix it if it is affected.
What it is: CVE-2025-61873 is a low-severity vulnerability in bestpractical Request Tracker, published on 16 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-61873 in the wild and no public exploit code.
Affected product: bestpractical 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-61873/ (Markdown: https://insights.sbomify.com/CVE-2025-61873/index.md)
Attackers can inject malicious formulas into CSV exports, potentially leading to code execution when tickets are exported as TSV.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2025-61873?
CVE-2025-61873 is a low-severity vulnerability in bestpractical Request Tracker, published on 16 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
Best Practical Request Tracker (RT) before 4.4.9, 5.0.9, and 6.0.2 allows CSV Injection via ticket values when TSV export is used.
Weakness: CWE-1236
Which versions are affected by CVE-2025-61873?
How do I fix CVE-2025-61873?
Upgrade to a fixed version.
Is CVE-2025-61873 being exploited?
There is no known exploitation of CVE-2025-61873 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2025-61873, DLA-4349-1, DSA-6031-1, DSA-6032-1, GHSA-3rc2-78m3-cqmh, UBUNTU-CVE-2025-61873.