CVE-2026-3359 is an unauthenticated SQL injection vulnerability in the Form Maker by 10Web plugin for WordPress. The flaw affects versions up to and including 1.15.42 and is caused by insufficient escaping of the user-controlled 'inputs' parameter together with inadequate use of prepared SQL statements in the query that consumes that parameter. Because attacker-supplied data can be appended into an existing SQL statement, a remote attacker can alter query structure and execute SQL injection techniques such as UNION-based or blind extraction to read arbitrary data from 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 repository is a small standalone Python exploit for CVE-2026-3359 affecting the Form Maker WordPress plugin. It contains three files: a README with setup and usage notes, a requirements.txt listing requests/beautifulsoup4/termcolor, and the main exploit script cve-2026-3359.py. The exploit is web-based and unauthenticated. Its workflow is: fetch the target homepage, extract a plugin-related fm_cookie_* cookie, scrape an ajaxnonce value from inline JavaScript, then submit a crafted POST request to the WordPress AJAX endpoint /wp-admin/admin-ajax.php using action=fm_reload_input and page=form_maker. The SQL injection is embedded inside the inputs[2|type_checkbox|all] parameter, which appears to influence backend SQL used to populate checkbox values. Capabilities are split into two modes. The -poc mode performs a basic boolean-style confirmation by injecting a SELECT 1 payload and checking whether the returned HTML contains checkbox input values equal to "1". The -qu mode goes beyond detection and attempts to extract data from the wp_users table by unioning user_login, user_email, and user_pass values, then printing the returned checkbox values. This makes the repository more than a detector: it includes active exploitation for limited database disclosure. The script supports either a single URL (-u) or a list of targets (-l). It also allows manual nonce override with -n. The code is operational but somewhat brittle: it assumes a specific form_id (6), a default wp_users table name, a particular response structure (JSON key "2" containing HTML), and successful retrieval of cookie/nonce from the homepage. Despite those assumptions, the repository’s purpose is clear: automate unauthenticated SQL injection testing and basic WordPress user data extraction against vulnerable Form Maker installations.
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.
9 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.