CVE-2025-0316 is an authentication bypass vulnerability in the WP Directorybox Manager plugin for WordPress affecting versions up to and including 2.5. The issue is caused by incorrect authentication logic in the 'wp_dp_enquiry_agent_contact_form_submit_callback' function. Due to this flaw, an unauthenticated attacker who knows or can obtain a valid username for an existing site account can abuse the vulnerable code path to authenticate as that user without providing legitimate credentials. The vulnerability can therefore result in full account compromise, including compromise of administrator accounts.
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 is an automated exploit toolkit targeting CVE-2025-0316, an authentication bypass vulnerability in the WordPress plugin WP Directorybox Manager (versions 2.5 and below). The main script, 'exploit.py', orchestrates the attack by first verifying the target is a WordPress site, then checking for the presence of the vulnerable plugin endpoint. It uses a user enumeration technique via the '?author=' URL parameter to discover valid usernames. For each username, it sends a crafted POST request to the '/wp-admin/admin-ajax.php' endpoint with a specific action and the username, attempting to trigger the authentication bypass and obtain a valid session cookie. Successful session cookies are saved to disk and can be used for browser auto-login to the WordPress admin panel. The exploit supports multi-threading, proxy usage, and random user-agents for stealth. Supporting modules handle user enumeration, plugin detection, session handling, and utility functions. The repository is structured with clear separation of concerns: 'exploit.py' (main logic), 'recon.py' (enumeration and plugin check), 'session_handler.py' (cookie management), 'helpers.py' (utility functions), and 'user_agents.txt' (user-agent pool). No hardcoded credentials or backdoors are present; the exploit is operational and automates a real-world attack chain.
2 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.