Loading vulnerability…
CVE-2025-10046 affects the ELEX WooCommerce Google Shopping (Google Product Feed) plugin for WordPress in all versions up to and including 1.4.3. The vulnerability is an SQL injection in the file_to_delete parameter caused by insufficient escaping of user-supplied input and inadequate preparation of the resulting SQL query. An authenticated attacker with Administrator-level access or higher can append additional SQL fragments to an existing query, enabling unauthorized interaction with the WordPress site's backend database, including extraction of sensitive information.
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 (1 hidden).
This repository contains an operational exploit for CVE-2025-10046, a high-severity SQL injection vulnerability in the ELEX WooCommerce Google Shopping (Product Feed) plugin for WordPress (version 1.4.3 and earlier). The exploit is implemented in C (exploit.c) and requires compilation with GCC and linking against libcurl. It targets the 'file_to_delete' parameter in the 'includes/elex-manage-feed-ajax.php' file, which is insufficiently sanitized before being used in SQL queries. The exploit requires administrator credentials (session cookies) to function, as the attack vector is authenticated. The tool automates sending SQL injection payloads to the vulnerable endpoint and can be run with various options for URL, cookies, and verbosity. The repository also includes a README.md with detailed usage instructions and a LICENSE file. No hardcoded IPs or domains are present, but the endpoint and parameter names are fingerprintable. The exploit is not part of a framework and is a standalone operational tool for exploiting this specific vulnerability.
6 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.