How severe is CVE-2019-15715?

CVE-2019-15715 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-15715?

CVE-2019-15715 affects the following packages: mantisbt/mantisbt (Packagist), mantisbt/mantisbt (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-15715?

Update mantisbt/mantisbt to 1.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15715 is resolved across your whole dependency graph.

How do I detect CVE-2019-15715 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-15715 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2019-15715 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2019-15715, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-15715?

CVE-2019-15715 has an EPSS (Exploit Prediction Scoring System) score of 30.0%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2019-15715?

CVE-2019-15715 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-15715 published, and has it been updated?

CVE-2019-15715 was published on October 9, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2019-15715 — mantisbt

HIGHFix: mantisbt/mantisbt@5fb9796

CVE-2019-15715 is a high-severity (CVSS 7.2) OS Command Injection vulnerability in mantisbt/mantisbt. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for mantisbt/mantisbt — see the affected versions and patch details below.

MantisBT Remote Code Execution

Also known asGHSA-v23g-wjvq-2fpf

Published

Oct 9, 2019

Updated

Oct 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

4 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

30.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘mantisbt/mantisbt🐘mantisbt/mantisbt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mantisbt/mantisbt`	all versions	1.3.20`composer require mantisbt/mantisbt:^1.3.20`
🐘Packagist	`mantisbt/mantisbt`	≥ 2.0.0&&< 2.22.1	2.22.1`composer require mantisbt/mantisbt:^2.22.1`

Affected Products

1 product · 2 configurations

Application

mantisbtmantisbt

≥ 2.0.0 && < 2.22.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-48818webappsphp

Mantis Bug Tracker 2.3.0 - Remote Code Execution (Unauthenticated)

by Nikolas Geiselman · Sep 18, 2020

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mantisbt/mantisbt to 1.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15715 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2019-15715 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.2/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-78OS Command Injection

Weaponization

No Nuclei template or Metasploit module yet. 4 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

mantisbt

4.8/10

Maintained10/10

Code-Review0/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Oct 9, 2019

First exploit

Sep 18, 2020

Last updated

Oct 20, 2026

Identifiers

CVE-2019-15715

GHSA-v23g-wjvq-2fpf

References

Advisorymantisbt.org · changelog page Advisorynvd.nist.gov · CVE 2019 15715 Fixgithub.com · 5fb979604d88c630343b3eaf2b435cd41918c501 Fixgithub.com · 7092573fac31eff41823f13540324db167c8bd52 Fixgithub.com · cebfb9acb3686e8904d80bd4bc80720b54ba08e5 Fixgithub.com · fc7668c8e45db55fc3a4b991ea99d2b80861a14c Reportmantisbt.org · view Reportmantisbt.org · view Packagegithub.com · mantisbt Evidencepacketstormsecurity.com · Mantis Bug Tracker 2.3.0 Remote Code Execution

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs affecting mantisbt/mantisbt are rated as high or higher (top: critical).

CVE-2026-52882CVE-2026-52883CVE-2026-52847CVE-2026-47156CVE-2026-62944CVE-2026-49280CVE-2026-47142CVE-2026-49273

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-15715 — mantisbt

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-15715 in your dependencies?