Cross-Site Scripting (XSS) in MantisBT Configuration Report page (CVE-2017-7309)
Summary
Cross-site scripting in MantisBT Configuration Report page (CVE-2017-7309). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.3.9 or later.
Original description
The description as published by the source.
A cross-site scripting (XSS) vulnerability in the MantisBT Configuration Report page (adm_config_report.php) allows remote attackers to inject arbitrary code (if CSP settings permit it) through a crafted 'config_option' parameter. This is fixed in 1.3.9, 2.1.3, and 2.2.3.
Source: NIST National Vulnerability Database 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-2017-7309 has been found in MantisBT Configuration Report page.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade MantisBT Configuration Report page to 1.3.9 or later.
If unsure, ask your IT team or search "MantisBT Configuration Report page CVE-2017-7309" on the vendor's site.
CVE-2017-7309 (MantisBT Configuration Report page) — CWE-79 / CVSS v3 4.8
Attack vector: remote (network-reachable)
Patched: 1.3.9 — 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 Configuration Report page.
Check the vendor advisory for the affected versions of MantisBT Configuration Report page.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 1.3.9.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで MantisBT Configuration Report page を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade MantisBT Configuration Report page to 1.3.9ステージング環境で 1.3.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory openwall.com
- advisory securityfocus.com
- patch mantisbt.org
- web securitytracker.com