Cross-Site Scripting (XSS) in mantisbt/mantisbt
Summary
Cross-site scripting in mantisbt/mantisbt (CVE-2026-40607). Risk of unauthorized operations or information disclosure. Exploitable via g_stored_query_create_threshold. Mitigation: upgrade to 2.28.2 or later.
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-40607 has been found in mantisbt/mantisbt.
Attackers can target a specific entry point like g_stored_query_create_threshold over the network to misuse the product.
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-40607" on the vendor's site.
CVE-2026-40607 (mantisbt/mantisbt) — CWE-79
Attack surface: g_stored_query_create_threshold / g_stored_query_create_shared_threshold / NOBODY
Patched: 2.28.2 — apply immediately
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. Attackers reach the vulnerable code path via g_stored_query_create_threshold.
Check the vendor advisory for the affected versions of mantisbt/mantisbt. Attack surface: g_stored_query_create_threshold / g_stored_query_create_shared_threshold / NOBODY.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.28.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1
Identify exposureidentify
grep -r 'mantisbt/mantisbt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mantisbt/mantisbtを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade mantisbt/mantisbt to 2.28.2ステージング環境で 2.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| composer | mantisbt/mantisbt |
< 2.28.2 |
2.28.2 |
| Packagist | mantisbt/mantisbt |
≥ 2.1.0, < 2.28.2 |
2.28.2 |
Original description The description as published by the source.
Mantis Bug Tracker (MantisBT) is an open source issue tracker. In versions 2.11.0 through 2.28.1, a Stored XSS vulnerability is caused by incorrect escaping of a saved filter's owner, allowing an attacker to inject arbitrary HTML on systems where $g_show_user_realname = ON. Note that By default, only users with Manager access level or above can save their filters publicly. This issue has been fixed in version 2.28.2. If developers are unable to update immediately, they can work around this issue by preventing display of users' real names (set $g_ show_user_realname = OFF; in configuration), and restricting the ability to store filters (set $g_stored_query_create_threshold / $g_stored_query_create_shared_threshold to NOBODY).
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web mantisbt.org
- web github.com