CVE-2006-6574: Mantis before 1.1.0a2 does not implement per-item access control for Issue History (Bug History), which allows

Q: How do I fix CVE-2006-6574?

mantis: upgrade to newer than 1.1.0a1. Exact commands for each OS are on this page.

Q: Is CVE-2006-6574 being exploited?

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

Q: What does CVE-2006-6574 affect?

CVE-2006-6574 affects mantis. Severity is medium (CVSS 5.0). Mantis before 1.1.0a2 does not implement per-item access control for Issue History (Bug History), which allows remote attackers to obtain sensitive information by reading the Change column, as demonstrated by the Change column of a custom f

Q: How urgent is CVE-2006-6574?

Priority 38/100. No elevated risk signals yet.

Routine

MEDIUM 5.0UPGRADE

CVE-2006-6574 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 1.1.0a2 does not implement per-item access control for Issue History (Bug History), which allows remote attackers to obtain sensitive information by reading the Change column, as demonstrated by the Change column of a custom field.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	2.0% (top 20%)
CISA exploited list	No
Published	2006-12-15
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

2006-12-15 19:28 UTCPublished CVE record published
2026-06-16 22:33 UTCUpdated Record last modified

mantis mantis UPGRADE

Affected: <= 1.1.0a1 · 1.0.0 · 1.0.0_rc1 · 1.0.0_rc2 · 1.0.0_rc3 · 1.0.0_rc4 · 1.0.0_rc5 · 1.0.0a1

Fixed in: newer than 1.1.0a1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.1.0a1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mantis

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mantis

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2006-6574?

mantis: upgrade to newer than 1.1.0a1. Exact commands for each OS are on this page.

Is CVE-2006-6574 being exploited?

CVE-2006-6574 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-2006-6574 affect?

CVE-2006-6574 affects mantis. Severity is medium (CVSS 5.0). Mantis before 1.1.0a2 does not implement per-item access control for Issue History (Bug History), which allows remote attackers to obtain sensitive information by reading the Change column, as demonstrated by the Change column of a custom f

How urgent is CVE-2006-6574?

Priority 38/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