Loading vulnerability…
CVE-2026-49079 is a critical SQL injection vulnerability affecting the WordPress JetSearch plugin in versions 3.5.17 and earlier. The issue is described as unauthenticated and remotely exploitable over the network with low attack complexity and no user interaction required. Specific vulnerable parameters or functions are not provided in the available content, but the flaw allows attacker-controlled input to be incorporated into backend SQL queries without proper sanitization or parameterization.
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.
Repository contains a single Python exploit script and a minimal README. The main file, CVE-2026-49079.py, is a standalone unauthenticated SQL injection exploit targeting the JetSearch WordPress plugin, claiming affected versions up to 3.5.17. The script is structured as a CLI tool with helper classes/methods for plugin detection, version checking, AJAX action discovery, action scanning, payload generation, and full exploitation. It uses requests.Session with a browser-like User-Agent and probes common WordPress plugin paths under /wp-content/plugins/ to identify JetSearch installations. It then attempts to retrieve the plugin PHP file to parse the version string and determine whether the target is within the claimed vulnerable range. The exploit also includes logic to crawl the target site to identify AJAX action names used by the plugin and supports multiple SQLi techniques: UNION-based, time-based blind, boolean-based blind, and error-based payloads. Based on the visible code, this is an operational exploit rather than a simple detector because it includes payload generation and exploitation workflow, though it is still a PoC-style standalone script rather than part of a larger framework.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.