Loading vulnerability…
ELEX WooCommerce Request a Quote for WordPress before version 2.4.1 improperly sanitizes and escapes a user-controlled parameter before incorporating it into an SQL query. This flaw permits unauthenticated SQL injection against the WordPress 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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This small repository contains an MIT license, a usage-oriented README, and one standalone Python 3 exploit script using only the standard library. The script targets CVE-2026-14962 in ELEX WooCommerce Request a Quote (plugin slug elex-request-a-quote) through the publicly accessible elex_raq_add_to_quote WordPress AJAX action. It first fingerprints the plugin through its readme, retrieves a public nonce from the site root or /shop/, manages cookies and redirects, and supports TLS verification bypass/retry handling. The exploit provides --test, --dump, --query, --sql, and --sleep modes. The test mode sends a crafted attribute value intended to expose the vulnerable preg_replace/format-string behavior present through 2.4.0; dump/query modes attempt error-based SQL disclosure, while sleep performs timing-based confirmation. This is functional offensive exploit code rather than only a scanner: it enables custom SQL-expression injection and attempts database/user-data extraction, although successful error-based dumping depends on exposed WordPress debug errors.
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, 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.