How severe is CVE-2017-7615?

CVE-2017-7615 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-7615?

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

How do I fix CVE-2017-7615?

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

How do I detect CVE-2017-7615 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mantisbt/mantisbt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2017-7615?

O3 pinpoints whether CVE-2017-7615 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2017-7615 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2017-7615, including 2 documented proof-of-concept exploits on Exploit-DB and 4 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-2017-7615?

CVE-2017-7615 has an EPSS (Exploit Prediction Scoring System) score of 90.9%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2017-7615?

CVE-2017-7615 is classified as CWE-640 (CWE-640). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2017-7615?

A Nuclei detection template exists for CVE-2017-7615, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-7615 published, and has it been updated?

CVE-2017-7615 was published on April 16, 2017 and was last updated on July 8, 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

CVE-2017-7615

HIGH

MantisBT allows arbitrary password reset

Also known asGHSA-252r-f55f-ff34

Published

Apr 16, 2017

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

90.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐘mantisbt/mantisbt🐘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 through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value to verify.php.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mantisbt/mantisbt`	≥ 1.3.0-rc.2&&< 1.3.10	1.3.10
🐘Packagist	`mantisbt/mantisbt`	≥ 2.0.0&&< 2.2.4	2.2.4
🐘Packagist	`mantisbt/mantisbt`	≥ 2.3.0&&< 2.3.1	2.3.1

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

EDB-41890webappsphp✓ Verified

Mantis Bug Tracker 1.3.0/2.3.0 - Password Reset

by hyp3rlinx · Apr 16, 2017

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mantisbt/mantisbt to 1.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7615 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-7615 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-7615. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

MantisBT through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value to verify.php.

O3 Security · Impact-Aware SCA

Is CVE-2017-7615 in your dependencies?

O3 detects CVE-2017-7615 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works