CVE-2006-6574

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2006-12-15 19:28 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:33 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.0% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2006-12-15 19:28 UTC

Last modified

2026-06-16 22:33 UTC

Exploit probability

2.0% · EPSS, next 30 days

Record status

Modified

Affected

• Mantis ≤ 1.1.0a1
• Mantis 1.0.0
• Mantis 1.0.0_rc1
• Mantis 1.0.0_rc2
• Mantis 1.0.0_rc3
• Mantis 1.0.0_rc4
• Mantis 1.0.0_rc5
• Mantis 1.0.0a1

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2006-6574.md and follow it. Check whether this project is affected by CVE-2006-6574. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge