CVE-2025-61873

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.

Published: 2026-01-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61873 is rated Low Risk (13/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.03%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-61873

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-17 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-61873

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.6 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.0 1.4 [email protected]

Weakness enumeration for CVE-2025-61873

OS Trackers for CVE-2025-61873

vendor priority summary link
debian not yet assigned CVE-2025-61873 not yet assigned priority: Debian including 2 source packages (request-tracker4, request-tracker5), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2025-61873
ubuntu medium CVE-2025-61873 medium priority: Ubuntu including 2 source packages (request-tracker4, request-tracker5), 13 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 11, ignored 2. https://ubuntu.com/security/CVE-2025-61873

Affected software / configurations for CVE-2025-61873

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-61873

cvelogic Threat Intelligence