Skip to content
Fencer Vulns
medium 4.8

CVE-2017-7309 json

MantisBT vulnerable to XSS through config_option parameter in adm_config_report.php

published 2017-03-31 9 y ago modified 2026-06-17 4 mo ago also GHSA-4w6c-3hcx-rfj5 , EUVD-2017-16336

cvss
4.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
63.3%
EPSS 63.3% chance of exploitation in 30 days, percentile 99.2%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist mantisbt/mantisbt 1.3.9, 2.1.3, 2.2.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-7309 updated cvss 4.7

mantis: three cross-site scripting issues fixed in 1.3.9, 2.1.3, 2.2.3

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

63.33% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • mantisbt.org http://www.mantisbt.org/bugs/view.php?id=22579 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 4.8 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N
GitHub 3.0 4.8 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist mantisbt/mantisbt
<1.3.9
>=2.1.0, <2.1.3
>=2.2.0, <2.2.3
1.3.9
2.1.3
2.2.3

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.