CVE-2017-7615 is an improper password recovery vulnerability in MantisBT affecting versions through 2.3.0. The flaw is in the password reset verification flow handled by verify.php, where an empty confirm_hash value is improperly accepted during account verification. By invoking the password reset verification process with a valid user identifier and a blank confirmation token, an unauthenticated attacker can bypass the intended reset validation logic and reach the account update stage. This can be used to reset another user's password, including an administrative account, resulting in unauthorized access.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit auxiliary module (mantisbt_password_reset.rb) that exploits an unauthenticated password reset vulnerability in MantisBT versions prior to 1.3.10, 2.2.4, and 2.3.1 (CVE-2017-7615). The module allows an attacker to reset the password of any user (given their user ID) by interacting with the MantisBT web interface via HTTP requests. The exploit works by first verifying the target is a MantisBT instance, then sending crafted requests to /verify.php and /account_update.php to reset the password. The module is written in Ruby and is intended to be used within the Metasploit framework. No hardcoded endpoints or IPs are present; the module operates against a user-supplied target. The exploit is operational and can be used to gain unauthorized access to user accounts on vulnerable MantisBT installations.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.