# CVE-2012-1119: Missing authorization in n/a

> Remote attackers can copy or clone bug reports in MantisBT without triggering audit logs, bypassing security monitoring.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8rvq-6w77-33qx

## What is CVE-2012-1119?

CVE-2012-1119 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 29 Jun 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MantisBT before 1.2.9 does not audit when users copy or clone a bug report, which makes it easier for remote attackers to copy bug reports without detection.

Weakness: CWE-264

## Which versions are affected by CVE-2012-1119?

It affects 1 product.


Products: Mantisbt Mantisbt.

## How do I fix CVE-2012-1119?

Upgrade to a fixed version.

## Is CVE-2012-1119 being exploited?

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

## Other vulnerabilities in Mantisbt Mantisbt

- [CVE-2019-15074](https://insights.sbomify.com/CVE-2019-15074/): MantisBT allows cross-site scripting (XSS) via crafted filename (critical 9.6)
- [CVE-2026-30849](https://insights.sbomify.com/CVE-2026-30849/): MantisBT SOAP API has an authentication bypass vulnerability on MySQL (critical 9.3)
- [CVE-2025-47776](https://insights.sbomify.com/CVE-2025-47776/): MantisBT: Authentication bypass for some passwords due to PHP type juggling (high 8.8)
- [CVE-2017-7615](https://insights.sbomify.com/CVE-2017-7615/): MantisBT allows arbitrary password reset (high 8.8)
- [CVE-2026-33517](https://insights.sbomify.com/CVE-2026-33517/): MantisBT Vulnerable to Stored HTML Injection in Tag Delete Confirmation (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1119 and fix it if it is affected.

What it is: CVE-2012-1119 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 29 Jun 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1119 in the wild and no public exploit code.

Affected product: Mantisbt Mantisbt. 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-2012-1119/ (Markdown: https://insights.sbomify.com/CVE-2012-1119/index.md)
```

## Sources

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

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