Patchfirst
CVE-2017-7309 EPSS 63.3%

A cross-site scripting (XSS) vulnerability in the MantisBT Configuration Report page (adm_config_report.php) allows…

Fix:upgrade mantisbt to 2.28.1 or later also fixes CVE-2017-7615, CVE-2026-30849 Details ↓

Summary

A cross-site scripting flaw in the MantisBT Configuration Report page (adm_config_report.php) lets an attacker inject script through a crafted 'config_option' parameter, with execution only possible where the Content Security Policy permits it. Exploitation requires a remote attacker to supply the crafted parameter.

Official description · CVE.org

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.

Breakdown
19.8 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Disclosed on 31 Mar 2017. No public exploit code or confirmed exploitation is recorded.

See the family tree

8 related vulnerabilities in the same code over 13 years. The latest fix listed for mantisbt/mantisbt is 2.4.1.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. CVE-2012-1119MantisBT before 1.2.9 does not audit when users copy or clone a…29 Jun 2012
  2. relatedMedium

    Why these are linked:

    CVE-2012-1122bug_actiongroup.php in MantisBT before 1.2.9 does not properly…29 Jun 2012
  3. same family
    CVE-2014-7146The XmlImportExport plugin in MantisBT 1.2.17 and earlier allows…18 Nov 2014
  4. relatedMedium

    Why these are linked:

    CVE-2014-8598The XML Import/Export plugin in MantisBT 1.2.x does not restrict…18 Nov 2014
  5. same family
    CVE-2014-9117MantisBT before 1.2.18 uses the public_key parameter value as…6 Dec 2014
  6. relatedMedium

    Why these are linked:

    CVE-2017-6973A cross-site scripting (XSS) vulnerability in the MantisBT…31 Mar 2017
  7. relatedHigh

    Why these are linked:

    • Fixed one release later2.1.2 → 2.1.3 (mantisbt/mantisbt)
    • Fixed one release later1.3.8 → 1.3.9 (mantisbt/mantisbt)
    • Same code patched: adm_config_report.php (machine-matched)Functions: check_config_valuecommit 034cd07commit 15e52e8commit 0243375commit c9e5b1d
    • Similar weakness in the same product (machine-matched)same package + description similarity
    This CVECVE-2017-7309A cross-site scripting (XSS) vulnerability in the MantisBT…31 Mar 2017
  8. same family
    CVE-2025-46556MantisBT is Vulnerable to Denial-of-Service (DoS) attack via…4 Nov 2025

Fixes in mantisbt/mantisbtPackagist package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 2.0.0-beta.2CVE-2016-711117 Feb 2017
  2. 2.2.2CVE-2017-697331 Mar 2017
  3. 2.2.3CVE-2017-724131 Mar 2017
  4. 2.2.3CVE-2017-730931 Mar 2017
  5. 2.3.1CVE-2017-761516 Apr 2017
  6. 2.3.2CVE-2017-789718 Apr 2017
  7. 2.4.1CVE-2017-762021 May 2017Latest listed

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: mantisbt/mantisbt.

Packagistmantisbt/mantisbtGHSA-4w6c-3hcx-rfj5

Upgrade to 2.28.1 or later

Fixes this CVE and 2 other known vulnerabilities in this package (CVE-2017-7615, CVE-2026-30849).

Set the version to 2.28.1 or later in your composer.json.

First fixed in 2.2.3 for CVE-2017-7309.

Affected versions, by release line

If you runUpgrade to
2.2.0 up to 2.2.32.28.1first fix for this CVE: 2.2.3
2.1.0 up to 2.1.3

Still affected on this line by CVE-2017-7615 (fixed in 2.2.4, a newer line); CVE-2026-30849 (fixed in 2.28.1, a newer line).

2.1.3
All versions before 1.3.9

Still affected on this line by CVE-2026-30849 (fixed in 2.28.1, a newer line).

1.3.10first fix for this CVE: 1.3.9

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

References

4 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close