# CVE-2006-6515: Missing authorization in n/a

> Default configuration allows reporters to send bug reminders, potentially bypassing intended privilege restrictions in Mantis.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xcmr-m9g5-7cxj

## What is CVE-2006-6515?

CVE-2006-6515 is a critical missing authorization vulnerability in n/a, published on 14 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mantis before 1.1.0a2 sets the default value of $g_bug_reminder_threshold to "reporter" instead of a more privileged role, which has unknown impact and attack vectors, possibly related to frequency of reminders.

## Which versions are affected by CVE-2006-6515?

It affects 1 product.


Products: Mantis Mantis.

## How do I fix CVE-2006-6515?

No fix has been published for CVE-2006-6515 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-6515 being exploited?

There is no known exploitation of CVE-2006-6515 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-0665](https://insights.sbomify.com/CVE-2006-0665/): Other in n/a (critical 10.0)
- [CVE-2002-1110](https://insights.sbomify.com/CVE-2002-1110/): SQL injection in n/a (critical 10.0)
- [CVE-2008-4687](https://insights.sbomify.com/CVE-2008-4687/): Code injection in n/a (critical 9.0)
- [CVE-2008-4689](https://insights.sbomify.com/CVE-2008-4689/): Auth bypass in n/a (high 7.5)
- [CVE-2008-3333](https://insights.sbomify.com/CVE-2008-3333/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6515 and fix it if it is affected.

What it is: CVE-2006-6515 is a critical missing authorization vulnerability in n/a, published on 14 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6515 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-6515/ (Markdown: https://insights.sbomify.com/CVE-2006-6515/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-6515
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-6515
- OSV: https://osv.dev/vulnerability/CVE-2006-6515

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-6515/
Summaries are generated and may contain mistakes; the official description above is the record.