← Back
CVE-2026-39960
medium
CVSS 5.4
Cross-Site Scripting (XSS) in mantisbt/mantisbt (CVE-2026-39960)
Summary
cross-site scripting in mantisbt/mantisbt (CVE-2026-39960). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.28.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-39960** has been found in mantisbt/mantisbt.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade mantisbt/mantisbt to **2.28.2** or later.
If unsure, ask your IT team or search "mantisbt/mantisbt CVE-2026-39960" on the vendor's site.
CVE-2026-39960 (mantisbt/mantisbt) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: `2.28.2` — apply immediately
Workaround: The default Content-Security Policy will block script execution.
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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in mantisbt/mantisbt.
📍 Affected scope
mantisbt/mantisbt — .
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.28.2**.
🛡️ Workaround
Workaround: The default Content-Security Policy will block script execution.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
The default Content-Security Policy will block script execution.パッチが適用されるまでの応急処置として、The default Content-Security Policy will block script execution. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade mantisbt/mantisbt to 2.28.2ステージング環境で 2.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
mantisbt/mantisbt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.28.2"}]}]
Packagist
mantisbt/mantisbt
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.28.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-39960
- package https://github.com/mantisbt/mantisbt
- web https://github.com/mantisbt/mantisbt/security/advisories/GHSA-qj6w-v29q-4rgx
- web https://github.com/mantisbt/mantisbt/commit/5fec0f448b7a7d7d539a6adb6dccceac4e4e4ab7
- web https://mantisbt.org/bugs/view.php?id=37003
- web https://github.com/advisories/GHSA-qj6w-v29q-4rgx