CVE-2023-41259

Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Disclosure via fake or spoofed RT email headers in an email message or a mail-gateway REST API call.

Published: 2023-11-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-41259 is rated Moderate Risk (47.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.72%). Review affected assets and schedule remediation.

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-2023-41259

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-06-15 0.11% 0.72% +0.60%
2 2026-01-10 0.19% 0.11% -0.08%
3 2025-11-21 — 0.19% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-41259

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-41259

OS Trackers for CVE-2023-41259

vendor priority summary link
alpine — CVE-2023-41259: 1 source package rows (rt4); 4 state rows across 4 repos (3.20-community, 3.21-community, 3.22-community, edge-community); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2023-41259
debian not yet assigned CVE-2023-41259 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-2023-41259
ubuntu medium CVE-2023-41259 medium priority: Ubuntu including 2 source packages (request-tracker4, request-tracker5), 24 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 8, released 8, ignored 7, DNE 1. https://ubuntu.com/security/CVE-2023-41259

Affected software / configurations for CVE-2023-41259

Vendor Product Version Raw CPE
bestpractical request_tracker < 4.4.7 cpe:2.3:a:bestpractical:request_tracker:*:*:*:*:*:*:*:*
bestpractical request_tracker >= 5.0.0, < 5.0.5 cpe:2.3:a:bestpractical:request_tracker:*:*:*:*:*:*:*:*

References for CVE-2023-41259

cvelogic Threat Intelligence