CVE-2004-2666: Mantis before 20041016 provides a complete Issue History (Bug History) in the web interface regardless of view

Routine

MEDIUM 5.0DOWNGRADE

CVE-2004-2666 is a medium-severity flaw (CVSS 5.0) affecting mantis. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Mantis before 20041016 provides a complete Issue History (Bug History) in the web interface regardless of view_history_threshold, which allows remote attackers to obtain sensitive information (private bug details) by visiting a bug's web page.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Published	2004-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: mantis

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2004-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:10 UTCUpdated Record last modified

mantis mantis DOWNGRADE

Affected: 0.9 · 0.9.1 · 0.10 · 0.10.1 · 0.10.2 · 0.11 · 0.11.1 · 0.12

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.9

1. Check installed version

apt-cache policy mantis || rpm -q mantis || mantis --version

2. No fixed release: DOWNGRADE to a release before 0.9 (Debian / Ubuntu)

apt-cache madison mantis sudo apt install mantis=<VERSION_BEFORE_0.9> sudo apt-mark hold mantis

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mantis sudo dnf downgrade mantis-<VERSION_BEFORE_0.9> sudo dnf versionlock add mantis

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2004-2666?

mantis: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2004-2666 being exploited?

CVE-2004-2666 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2004-2666 affect?

CVE-2004-2666 affects mantis. Severity is medium (CVSS 5.0). Mantis before 20041016 provides a complete Issue History (Bug History) in the web interface regardless of view_history_threshold, which allows remote attackers to obtain sensitive information (private bug details) by visiting a bug's web pa

How urgent is CVE-2004-2666?

Priority 35/100. No elevated risk signals yet.

Related CVEs

CVE-2019-16569 MEDIUM 4.3 UPGRADE A cross-site request forgery vulnerability in Jenkins Mantis Plugin 0.26 and earlier allows attackers to conne
CVE-2008-4689 HIGH 7.5 UPGRADE Mantis before 1.1.3 does not unset the session cookie during logout, which makes it easier for remote attacker
CVE-2008-4688 MEDIUM 5.0 UPGRADE core/string_api.php in Mantis before 1.1.3 does not check the privileges of the viewer before composing a link
CVE-2008-4687 HIGH 9.0 UPGRADE manage_proj_page.php in Mantis before 1.1.4 allows remote authenticated users to execute arbitrary code via a
CVE-2008-3333 HIGH 7.5 UPGRADE Directory traversal vulnerability in core/lang_api.php in Mantis before 1.1.2 allows remote attackers to inclu

References

← Back to latest CVEs