Skip to content
Fencer Intel
medium 6.1

CVE-2022-25802 json

Best Practical Request Tracker (RT) before 4.4.6 and 5.x before 5.0.3 allows XSS via a crafted content type for an attachment.

published 4y ago modified 4mo ago also EUVD-2022-30442

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

Best Practical Request Tracker (RT) before 4.4.6 and 5.x before 5.0.3 allows XSS via a crafted content type for an attachment.

Patch / fix

  • bestpractical request_tracker 4.4.6, 5.0.3
  • request-tracker4 Debian 12 4.4.6+dfsg-1
  • request-tracker5 Debian 14, Debian 13, Debian 12 5.0.3+dfsg-1

debian advisories DEBIAN-CVE-2022-25802

  • request-tracker4 Ubuntu 20.04 LTS 4.4.3-2+deb10u3build0.20.04.1
  • request-tracker4 Ubuntu 22.04 LTS 4.4.4+dfsg-2ubuntu1.22.04.1
  • request-tracker4 Ubuntu Pro 18.04 LTS 4.4.2-2ubuntu0.1~esm1
  • request-tracker5 Ubuntu Pro 22.04 LTS 5.0.1+dfsg-1ubuntu1+esm1

ubuntu advisories UBUNTU-CVE-2022-25802

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • rt4 Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 4.4.7-r0

alpine advisories ALPINE-CVE-2022-25802

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-25802 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.