# CVE-2025-62520: MantisBT unauthorized disclosure of private project column configuration

> Non-admin users can view private project column configurations via the Copy From action, exposing sensitive settings.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 4 Nov 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-g582-8vwr-68h2

## What is CVE-2025-62520?

CVE-2025-62520 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mantis Bug Tracker (MantisBT) is an open source issue tracker. In versions 2.27.1 and below, due to insufficient access-level checks, any non-admin user with access to manage_config_columns_page.php can use the Copy From action to retrieve the columns configuration from a private project they have no access to. This issue is fixed in version 2.27.2.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2025-62520?

2 open source packages ship an affected version, including mantisbt/mantisbt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mantisbt/mantisbt` | Packagist | All versions | 2.27.2 |
| `mantisbt/mantisbt` | Packagist | All versions | 2.27.2 |

Products: Mantisbt Mantisbt.

## How do I fix CVE-2025-62520?

Upgrade mantisbt/mantisbt to 2.27.2 or later.

## Is CVE-2025-62520 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62520 exists.

## 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-2025-62520 and fix it if it is affected.

What it is: CVE-2025-62520 is a medium-severity missing authorization vulnerability in Mantisbt Mantisbt, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62520 exists.

Affected packages and fixed versions:
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.27.2
- mantisbt/mantisbt (Packagist): affected all versions; fixed in 2.27.2

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-2025-62520/ (Markdown: https://insights.sbomify.com/CVE-2025-62520/index.md)
```

## Sources

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

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