CVE-2017-6973
MEDIUMCVE-2017-6973 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in mantisbt/mantisbt. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2017-6973 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
MantisBT XSS via adm_config_report.php's action parameter
Blast Radius
mantisbt/mantisbt🐘mantisbt/mantisbt🐘mantisbt/mantisbtReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A cross-site scripting (XSS) vulnerability in the MantisBT Configuration Report page (adm_config_report.php) allows remote attackers to inject arbitrary code through a crafted 'action' parameter. This is fixed in 1.3.8, 2.1.2, and 2.2.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | mantisbt/mantisbt | all versions | 1.3.8 |
| 🐘Packagist | mantisbt/mantisbt | ≥ 2.0.0&&< 2.1.2 | 2.1.2 |
| 🐘Packagist | mantisbt/mantisbt | ≥ 2.2.0&&< 2.2.2 | 2.2.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mantisbt/mantisbt to 1.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-6973 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-6973 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2017-6973. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2017-6973 in your dependencies?
O3 detects CVE-2017-6973 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.