CVE-2025-30087

Best Practical RT (Request Tracker) 4.4 through 4.4.7 and 5.0 through 5.0.7 allows XSS via injection of crafted parameters in a search URL.

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

CVE-2025-30087 is rated Moderate Risk (46.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.27%). 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-2025-30087

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-09 0.63% 0.27% -0.36%
2 2026-06-08 0.31% 0.63% +0.32%
3 2026-03-24 — 0.31% —

Full EPSS history (8 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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: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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
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.
 3.9 2.7 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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: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: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:L)
Some sensitive info could get out, but not a total data dump.
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.
 2.8 2.7 [email protected]

Weakness enumeration for CVE-2025-30087

OS Trackers for CVE-2025-30087

vendor priority summary link
debian not yet assigned CVE-2025-30087 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-30087
ubuntu medium CVE-2025-30087 medium priority: Ubuntu including 2 source packages (request-tracker4, request-tracker5), 16 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 6, released 5, ignored 3, DNE 1, not-affected 1. https://ubuntu.com/security/CVE-2025-30087

Affected software / configurations for CVE-2025-30087

Vendor Product Version Raw CPE
bestpractical request_tracker >= 4.4.0, < 4.4.8 cpe:2.3:a:bestpractical:request_tracker:*:*:*:*:*:*:*:*
bestpractical request_tracker >= 5.0.0, < 5.0.8 cpe:2.3:a:bestpractical:request_tracker:*:*:*:*:*:*:*:*

References for CVE-2025-30087

cvelogic Threat Intelligence