# CVE-2026-44655: MantisBT: Stored XSS on Move Attachments Admin Page

> An attacker with manager or admin access can inject HTML into the Move Attachments admin page via unescaped project names, potentially leading to script execution.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-7mqj-8gj2-cg59

## What is CVE-2026-44655?

CVE-2026-44655 is a high-severity cross-site scripting vulnerability in mantisbt, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Mantis Bug Tracker (MantisBT) is an open source issue tracker. From 1.3.0 to 2.28.1, unescaped Project Name allows an attacker that can set it (which typically requires manager or administrator access level) to inject HTML in Move Attachments admin page. This vulnerability is fixed in 2.28.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-44655?

2 open source packages ship an affected version, including mantisbt/mantisbt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mantisbt/mantisbt` | Packagist | From 1.3.0 | 2.28.2 |
| `mantisbt/mantisbt` | Packagist | From 1.3.0 | 2.28.2 |

## How do I fix CVE-2026-44655?

Upgrade mantisbt/mantisbt to 2.28.2 or later.

## Is CVE-2026-44655 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44655 and fix it if it is affected.

What it is: CVE-2026-44655 is a high-severity cross-site scripting vulnerability in mantisbt, published on 28 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44655 in the wild and no public exploit code.

Affected packages and fixed versions:
- mantisbt/mantisbt (Packagist): affected from 1.3.0; fixed in 2.28.2
- mantisbt/mantisbt (Packagist): affected from 1.3.0; fixed in 2.28.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-2026-44655/ (Markdown: https://insights.sbomify.com/CVE-2026-44655/index.md)
```

## Sources

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

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