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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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 91.2%, 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 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-2017-7615 — mantisbt

HIGH

CVE-2017-7615 is a high-severity (CVSS 8.8) CWE-640 vulnerability in mantisbt/mantisbt. 6 public exploit references exist, so weaponization risk is real. A fix is available for mantisbt/mantisbt — see the affected versions and patch details below.

MantisBT allows arbitrary password reset

Also known asGHSA-252r-f55f-ff34

Published

Apr 16, 2017

Updated

Oct 20, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

6 known

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

EPSS Exploitation Probability

via FIRST.org ↗

91.2%probability of exploitation in next 30 days

Very High Risk+0.10%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2017-7615 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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`composer require mantisbt/mantisbt:^1.3.10`
🐘Packagist	`mantisbt/mantisbt`	≥ 2.0.0&&< 2.2.4	2.2.4`composer require mantisbt/mantisbt:^2.2.4`
🐘Packagist	`mantisbt/mantisbt`	≥ 2.3.0&&< 2.3.1	2.3.1`composer require mantisbt/mantisbt:^2.3.1`

Affected Products

1 product · 1 configurations

Application

mantisbtmantisbt

≤ 2.3.0

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

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 to detect CVE-2017-7615

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2017-7615 -u https://target

Template: MantisBT <=2.30 - Arbitrary Password Reset/Admin Access
Severity: high
Impact: Successful exploitation of this vulnerability can lead to unauthorized password resets and unauthorized administrative access.
Remediation: Upgrade MantisBT to a version higher than 2.30 to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (bp0lr, dwisiswant0), MIT licensed. View the full template. Scan only systems you are authorised to test.

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?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

Weaponization

OpenSSF Scorecard

Package health score

mantisbt

4.8/10

Maintained10/10

Code-Review0/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Apr 16, 2017

First exploit

Sep 18, 2020

Last updated

Oct 20, 2026

Identifiers

CVE-2017-7615

GHSA-252r-f55f-ff34

References

Advisoryopenwall.com Advisorysecurityfocus.com Advisorynvd.nist.gov Fixmantisbt.org Webexploit-db.com Packagegithub.com Evidencehyp3rlinx.altervista.org Evidencepacketstormsecurity.com Evidenceexploit-db.com

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-2017-7615 — 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

How to detect CVE-2017-7615

Frequently Asked Questions

Is CVE-2017-7615 in your dependencies?