Loading vulnerability…
CVE-2025-3604 affects the Flynax Bridge plugin for WordPress in all versions up to and including 2.2.0. The vulnerability stems from improper validation of user identity before allowing updates to account details such as the email address. As a result, an unauthenticated attacker can modify the email address associated with an arbitrary user account, including administrator accounts. After changing the victim account's email address, the attacker can trigger the WordPress password reset workflow and receive the reset link at the attacker-controlled address, enabling takeover of the targeted account. The issue is therefore a privilege-escalation flaw realized through unauthorized account modification and subsequent account takeover.
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.
This repository contains a Python exploit script (CVE-2025-3604.py) targeting the Flynax Bridge WordPress plugin (versions <= 2.2.0). The exploit leverages an unauthenticated privilege escalation vulnerability that allows an attacker to change the email address of any user, including administrators, by sending a crafted POST request to the plugin's request.php endpoint. After changing the email, the attacker can initiate a password reset to fully compromise the account. The script checks the plugin version by fetching the readme.txt file, then attempts the exploit if the version is vulnerable. The repository also includes a README.md with usage instructions and a LICENSE file. The main attack vector is network-based, exploiting a web endpoint without authentication.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.