Loading vulnerability…
The WP-Recall plugin for WordPress, up to and including version 16.26.10, is vulnerable to SQL Injection via the 'databeat' parameter. The vulnerability arises from insufficient escaping and lack of proper preparation of SQL queries, allowing unauthenticated attackers to inject arbitrary SQL commands through crafted input to the 'databeat' parameter.
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 proof-of-concept exploit for CVE-2025-1323, a SQL injection vulnerability in the WP-Recall WordPress plugin. The main file, CVE-2025-1323.py, constructs a specially crafted POST request to the /wp-admin/admin-ajax.php endpoint, embedding a SQL injection payload in the 'last_activity' field of a JSON structure. The exploit requires the attacker to provide the target URL and a valid ajax_nonce value. If successful, the exploit can leak database information, such as the current database user. The repository also includes a README.md with usage instructions and a legal disclaimer. No hardcoded endpoints or credentials are present; the script is interactive and requires user input for the target and nonce. The exploit is a proof-of-concept and does not include advanced payloads or automation for extracting further data.
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 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.