CVE-2026-4798 is a high-severity time-based blind SQL injection vulnerability in the Avada Builder plugin for WordPress. It affects versions up to and including 3.15.1. The flaw is caused by insufficient escaping of the user-controlled product_order parameter together with inadequate use of prepared statements in an existing SQL query. As a result, unauthenticated attackers can inject SQL syntax into backend database queries and use timing-based techniques to infer database contents without direct query output. The vulnerability is only reachable in environments where WooCommerce had previously been used and was later deactivated. Successful exploitation can expose sensitive information stored in the WordPress database, including credential material such as password hashes.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A time-based blind SQL injection vulnerability in Avada Builder mentioned as a related issue patched in version 3.15.2.
A time-based SQL injection vulnerability in the Avada Builder WordPress plugin that allows unauthenticated attackers to extract sensitive database information under specific conditions.
A high-severity unauthenticated SQL injection vulnerability in the Avada Builder WordPress plugin that could allow attackers to extract sensitive data, including password hashes, from the website database.
A high-severity SQL injection vulnerability in the Avada Builder WordPress plugin that can be exploited by unauthenticated attackers to extract sensitive database data, including hashed passwords.
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.