dbcve.org
Request TrackerApplication · Bestpractical

CVE-2025-30087

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-28
Fix available
A fix is available. Upgrade to 4.4.8 / 5.0.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Best Practical RT (Request Tracker) versions 4.4-4.4.7 and 5.0-5.0.7 contain a Cross-Site Scripting (XSS) vulnerability in the search URL functionality. Attackers can inject malicious scripts through crafted parameters in search URLs, potentially executing arbitrary JavaScript in the context of authenticated users' browsers.

MitigationUpgrade to RT 4.4.8 or 5.0.8 or later, which contain the security fix for this vulnerability. Until patched, consider implementing Web Application Firewall rules to filter malicious search parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Request TrackerApplication
Affected:>= 4.4.0, < 4.4.8>= 5.0.0, < 5.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your installed RT version
    Log into RT as an administrator and navigate to Tools > System Configuration > About, or check the RT version file in your installation directory (such as lib/RT.pm or etc/RT_Config.pm)
    Affected if The displayed version is 4.4.0 through 4.4.7, or 5.0.0 through 5.0.7 (versions prior to 4.4.8 or 5.0.8)
  2. Verify search functionality is accessible
    Confirm that the RT search builder or simple search feature is enabled for at least some users. Check in Tools > Configuration > Global > Web interface > Web home. Also ensure that users have Search or ShowSearch menus permissions.
    Affected if The search functionality is enabled and accessible to authenticated users (this is the default configuration)
  3. Inspect search URL parameters
    Perform a test search using the RT search interface (such as searching for tickets by any field). Observe the resulting URL in the browser address bar for query parameters such as q, Query, or search parameters.
    Affected if The URL contains unsanitized user-supplied parameters that could contain script injection (for example, if the URL directly reflects back URL parameters without encoding)
  4. Review RT configuration for XSS protections
    Examine your RT_SiteConfig.pm or RT_Config.pm for settings related to input sanitization, such as $DisableAutocomplete, $CanonicalizeRedirectURLs, or custom JavaScript filters in the Mason config.
    Affected if No additional XSS protections are configured beyond default settings, and the version falls within the vulnerable range

You are affected if your installed RT version is 4.4.0-4.4.7 or 5.0.0-5.0.7 and the search functionality is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.8 / 5.0.8 or later
Fixed in 4.4.85.0.8
Interim mitigation

Upgrade to RT 4.4.8 or 5.0.8 or later, which contain the security fix for this vulnerability. Until patched, consider implementing Web Application Firewall rules to filter malicious search parameters.

Recommended fix High confidence

RT 4.4.8 or RT 5.0.8

  1. 1. Back up your RT database and configuration files before upgrading.
  2. 2. Download RT 4.4.8 (for 4.4.x users) or RT 5.0.8 (for 5.0.x users) from the official Best Practical website or repository.
  3. 3. Stop the RT web server and any background workers.
  4. 4. Install the new version following the standard RT upgrade documentation at docs.bestpractical.com.
  5. 5. Run the RT upgrade scripts (rt-setup-database --upgrade) to apply any database schema changes.
  6. 6. Restart the RT web server and background workers.
  7. 7. Verify the upgrade was successful by logging in and testing search functionality.
  8. 8. Clear any cached templates or tmp files to ensure the patched code is used.
Caveat Minor version upgrades within 4.4.x or 5.0.x typically have minimal breaking changes; review the release notes for any noted changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Request Tracker Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30087 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data