# CVE-2022-28508: MantisBT vulnerable to XSS via unescaped output in browser_search_plugin.php

> An attacker can inject malicious scripts via the return parameter in the search plugin, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wfg2-2wmw-6894

## What is CVE-2022-28508?

CVE-2022-28508 is a medium-severity cross-site scripting vulnerability in Mantisbt Mantisbt, published on 4 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An XSS issue was discovered in browser_search_plugin.php in MantisBT before 2.25.2. Unescaped output of the return parameter allows an attacker to inject code into a hidden input field.

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

## Which versions are affected by CVE-2022-28508?

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 to 2.25.2 | None |
| `mantisbt/mantisbt` | Packagist | All versions to 2.25.2 | None |

Products: Mantisbt Mantisbt.

## How do I fix CVE-2022-28508?

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

## Is CVE-2022-28508 being exploited?

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

Public exploit code:

- CVE-2022-28508 (github_poc): https://github.com/YSah44/CVE-2022-28508
- MantisBT < 2.25.2 - Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-28508.yaml

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

What it is: CVE-2022-28508 is a medium-severity cross-site scripting vulnerability in Mantisbt Mantisbt, published on 4 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28508 exists.

Affected packages and fixed versions:
- mantisbt/mantisbt (Packagist): affected all versions up to 2.25.2; no fix listed
- mantisbt/mantisbt (Packagist): affected all versions up to 2.25.2; no fix listed

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

## Sources

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

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