dbcve.org
Request TrackerApplication · Bestpractical

CVE-2026-6841

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-21
Fix available
A fix is available. Upgrade to 5.0.10 / 6.0.3 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
Request Tracker is vulnerable to a reflected cross-site scripting (XSS) vulnerability via the "Page" parameter in GET requests. An attacker can craft a URL that, when opened, results in arbitrary JavaScript execution in the victim’s browser. This vulnerability affects versions from 5.0.4 up to 5.0.9 and from 6.0.0 up to 6.0.2.

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

Reflected XSS vulnerability in Request Tracker's web interface where the 'Page' GET parameter lacks proper input sanitization, allowing injection of malicious JavaScript that executes in victim's browser when clicking a crafted URL.

MitigationUpgrade to the latest Request Tracker version that includes the patch for this vulnerability. As an interim measure, implement input validation on the Page parameter and deploy Content Security Policy headers to mitigate XSS execution.

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:>= 5.0.4, < 5.0.10>= 6.0.0, < 6.0.3

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. Identify installed Request Tracker version
    Locate the RT version file or check the About page in the RT web interface. Common locations: /opt/rt5/lib/RT.pm or the RT version displayed in the web admin interface under Help > About.
    Affected if The installed version falls within >= 5.0.4, < 5.0.10 OR >= 6.0.0, < 6.0.3.
  2. Confirm web interface is enabled
    Verify that the Request Tracker web interface (usually Apache or nginx with mod_perl/fastcgi) is running and accessible.
    Affected if The RT web interface is accessible to users who could be targeted with a malicious URL.
  3. Test Page parameter reflection
    Send a GET request to any RT page with an arbitrary value in the Page parameter, such as: GET /rt/?Page=TestXSS123. Inspect the HTTP response body to see if the value is reflected exactly as submitted without encoding or sanitization.
    Affected if The Page parameter value appears verbatim in the response HTML without being escaped or encoded.
  4. Verify no output encoding is applied
    Examine the RT configuration files (RT_SiteConfig.pm) or the underlying code handling the Page parameter to confirm whether output encoding is being applied before reflection.
    Affected if No output encoding/escaping is performed on the Page parameter before it is included in the HTTP response.

You are affected if you are running a version of Request Tracker between 5.0.4-5.0.9 or 6.0.0-6.0.2 AND the Page parameter is reflected in the web interface response without sanitization.

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 5.0.10 / 6.0.3 or later
Fixed in 5.0.106.0.3
Interim mitigation

Upgrade to the latest Request Tracker version that includes the patch for this vulnerability. As an interim measure, implement input validation on the Page parameter and deploy Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Request Tracker 5.0.10 or 6.0.3 (depending on your current major version branch)

  1. 1. Identify your current Request Tracker version by checking the RT version file or admin interface
  2. 2. Create a complete backup of your RT database and configuration files
  3. 3. If running 5.0.4-5.0.9, plan upgrade to RT 5.0.10
  4. 4. If running 6.0.0-6.0.2, plan upgrade to RT 6.0.3
  5. 5. Follow standard RT upgrade procedure: stop RT services, install new version, run database upgrade scripts (rt-setup-database --upgrade), restart services
  6. 6. Verify the upgrade was successful and test that the "Page" parameter is now properly sanitized
Caveat Review RT migration notes between minor versions for any configuration or dependency 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6841 — 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-2026-6841 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