Vulnerability in mantisbt/mantisbt (CVE-2026-42071)
Summary
Vulnerability in mantisbt/mantisbt (CVE-2026-42071). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/rest/issues/{id}/files. 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. From 2.23.0 to 2.28.1, a missing authorization check in MantisBT's file visibility function allows any authenticated user (REPORTER+) to download attachments on private bugnotes they should not be able to access, via the REST API endpoint GET /api/rest/issues/{id}/files and SOAP API mc_issue_attachment_get endpoint. This vulnerability is fixed in 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-42071 has been found in mantisbt/mantisbt.
Attackers can target a specific entry point like GET /api/rest/issues/{id}/files 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-42071" on the vendor's site.
CVE-2026-42071 (mantisbt/mantisbt) — CWE-862
Attack surface: GET /api/rest/issues/{id}/files
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.
A vulnerability (CWE-862) exists in mantisbt/mantisbt. Attackers reach the vulnerable code path via GET /api/rest/issues/{id}/files.
Check the vendor advisory for the affected versions of mantisbt/mantisbt. Attack surface: GET /api/rest/issues/{id}/files.
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 GET /api/rest/issues/{id}/files requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/rest/issues/{id}/files' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/rest/issues/{id}/filesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade mantisbt/mantisbt to 2.28.2ステージング環境で 2.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/rest/issues/{id}/files on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web mantisbt.org
- web mantisbt.org
- web mantisbt.org
- web github.com