CVE-2019-15074 json
MantisBT allows cross-site scripting (XSS) via crafted filename
published 7y ago modified 4mo ago also GHSA-gg4j-279j-22ph , EUVD-2019-6154
- cvss
- 9.6
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
The Timeline feature in my_view_page.php in MantisBT through 2.21.1 has a stored cross-site scripting (XSS) vulnerability, allowing execution of arbitrary code (if CSP settings permit it) after uploading an attachment with a crafted filename. The code is executed for any user having visibility to the issue, whenever My View Page is displayed.
Patch / fix
Is CVE-2019-15074 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.07% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- mantisbt.org https://mantisbt.org/bugs/view.php?id=25995 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.6 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | mantisbt/mantisbt | <2.21.2 |
2.21.2 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/mantisbt/mantisbt/commit/9cee1971c498bbe0a72bca1c773fae50171d8c27
web, patch, third-party-advisory
-
mantisbt.org
/bugs/view.php?id=25995
web, exploit, issue-tracking, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-15074
advisory
-
github.com
/mantisbt/mantisbt
package
Sources
- CVE List CVE-2019-15074
- GitHub Advisory GHSA-gg4j-279j-22ph
- NVD CVE-2019-15074
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.