Skip to content
Fencer Intel
high 7.2

CVE-2019-15715 in the critical feed json

MantisBT Remote Code Execution

published 7y ago modified 4mo ago also GHSA-v23g-wjvq-2fpf , EUVD-2019-6651

cvss
7.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
30.0%
EPSS 30.0% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

MantisBT before 1.3.20 and 2.22.1 allows Post Authentication Command Injection, leading to Remote Code Execution.

Patch / fix

  • packagist mantisbt/mantisbt 1.3.20, 2.22.1
  • mantisbt mantisbt 1.3.20, 2.22.1

Is CVE-2019-15715 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 Fencer

Timeline

  1. Published
  2. First public exploit (EDB-48818)

Exploit prediction

30.00% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-48818 Mantis Bug Tracker 2.3.0 - Remote Code Execution (Unauthenticated) webapps, 2020-09-18
  • mantisbt.org https://mantisbt.org/bugs/view.php?id=26091 referenced PoC, tagged "exploit" by a source, unverified
  • mantisbt.org https://mantisbt.org/bugs/view.php?id=26162 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/159219/Mantis-Bug-Tracker-2.3.0-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist mantisbt/mantisbt
<1.3.20
>=2.0.0, <2.22.1
1.3.20
2.22.1

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

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.