Information Disclosure in mantisbt/mantisbt (CVE-2026-34744)
Summary
Vulnerability in mantisbt/mantisbt (CVE-2026-34744). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.28.2 or later.
Original description
The description as published by the source.
MantisBT permits a user to list and download their own attachments from an Issue created by another user, even after that Issue becomes private and direct access to it is denied.
Impact
The loss of confidentiality caused by this vulnerability is minimal, considering that only the attachments that were previously uploaded by the user themselves remains accessible.
Patches
- de7bdeec36de066235e38a77bf056917d951c84d
Workarounds
None.
Credits
Thanks to Vishal Shukla for discovering and responsibly reporting the issue.
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-34744 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-34744" on the vendor's site.
CVE-2026-34744 (mantisbt/mantisbt) — CWE-200
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.
Information disclosure (CWE-200) 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.
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
-
1Identify exposure identify
grep -r 'mantisbt/mantisbt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mantisbt/mantisbtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mantisbt/mantisbt to 2.28.2ステージング環境で 2.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com