CVE-2016-7111 json
MantisBT XSS through weak CSP when using Gravatar plugin
published 2017-02-17 9 y ago modified 2026-06-17 4 mo ago also GHSA-8vx9-hcvq-gfv8 , EUVD-2016-7990
- cvss
- 4.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
MantisBT before 1.3.1 and 2.x before 2.0.0-beta.2 uses a weak Content Security Policy when using the Gravatar plugin, which allows remote attackers to conduct cross-site scripting (XSS) attacks via unspecified vectors.
Patch / fix
- packagist mantisbt/mantisbt 1.3.1, 2.0.0-beta.2
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.7 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 4.7 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | mantisbt/mantisbt | <1.3.1 >=2.0.0-beta.1, <2.0.0-beta.2 |
1.3.1 2.0.0-beta.2 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/mantisbt/mantisbt/commit/b3511d2f
patch
-
openwall.com
/lists/oss-security/2016/08/29/2
mailing-list, web, patch, third-party-advisory
-
mantisbt.org
/bugs/view.php?id=21263
web, patch, vendor-advisory
-
github.com
/mantisbt/mantisbt/commit/b3511d2feb47eaee41feb5f69cf3c8a2c9acd229
web
-
openwall.com
/lists/oss-security/2016/08/28/1
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2016-7111
advisory
-
github.com
/mantisbt/mantisbt
package
Sources
- CVE List CVE-2016-7111
- GitHub Advisory GHSA-8vx9-hcvq-gfv8
- NVD CVE-2016-7111
Fencer Intel 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.