Loading vulnerability…
The WP-Advanced-Search WordPress plugin versions prior to 3.3.9.2 are vulnerable to SQL injection due to insufficient sanitization and escaping of the 't' parameter before it is used in SQL statements. This flaw allows unauthenticated attackers to inject arbitrary SQL queries into the application's database.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
Repository contains a small Python proof-of-concept exploit for CVE-2024-9796 targeting a WordPress plugin endpoint. Structure: (1) `CVE-2024-9796.py` (interactive PoC) and (2) `README.md` (Spanish description and usage). The script prompts for a WordPress host/IP, normalizes it to a base URL, then sends a crafted `requests.get()` to `/wp-content/plugins/wp-advanced-search/class.inc/autocompletion/autocompletion-PHP5.5.php` with query parameters where `t` carries a UNION-based SQL injection. Two built-in payload choices are provided: dumping `wp_users.user_pass` values (password hashes) or extracting the current database name. Output is the raw HTTP response body printed to stdout. No scanning, authentication bypass, or post-exploitation is included; it is a direct single-endpoint SQLi PoC.
This repository contains a proof-of-concept (PoC) exploit for CVE-2024-9796, targeting the WP-Advanced-Search WordPress plugin versions prior to 3.3.9.2. The exploit is implemented in a single Python script (poc.py) and is accompanied by a README.md file describing its usage and purpose. The script takes a target IP address as input and sends a crafted HTTP GET request to the vulnerable autocompletion-PHP5.5.php endpoint of the plugin, exploiting an unauthenticated SQL injection vulnerability. If the target is vulnerable, the script extracts and prints WordPress usernames and their password hashes. The exploit does not require authentication and is designed for educational and testing purposes. The repository is straightforward, with clear separation between documentation and exploit code, and does not include any payload customization or advanced post-exploitation features.
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.