Cross-Site Scripting (XSS) in mantisbt/mantisbt (CVE-2026-34463)
Summary
Cross-site scripting in mantisbt/mantisbt (CVE-2026-34463). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.28.2 or later.
Original description
The description as published by the source.
Mantis Bug Tracker (MantisBT) is an open source issue tracker. Versions 2.28.1 and prior contain a Stored XSS vulnerability. When cloning an issue originating from a Project other than the current one, the clone form (bug_report_page.php) prepends the source Project name before the category selector without proper escaping, allowing an attacker able to to inject HTML if they can set the Project's name (which typically requires manager or administrator access level). This issue has been resolved in version 2.28.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-34463 has been found in mantisbt/mantisbt.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mantisbt/mantisbt to 2.28.2 or later.
If unsure, ask your IT team or search "mantisbt/mantisbt CVE-2026-34463" on the vendor's site.
CVE-2026-34463 (mantisbt/mantisbt) — CWE-79
Patched: 2.28.2 — apply immediately
Workaround: Make sure Project names do not contain any HTML tags.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in mantisbt/mantisbt.
Check the vendor advisory for the affected versions of mantisbt/mantisbt.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.28.2.
Workaround: Make sure Project names do not contain any HTML tags.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mantisbt/mantisbt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mantisbt/mantisbt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mantisbt/mantisbtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Make sure Project names do not contain any HTML tags.パッチが適用されるまでの応急処置として、Make sure Project names do not contain any HTML tags. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade mantisbt/mantisbt to 2.28.2ステージング環境で 2.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web mantisbt.org
- web github.com