WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More versions through 2.0.2 contain a reflected cross-site scripting vulnerability in processing of the page_title POST parameter. Insufficient sanitization of attacker-controlled input and output escaping when the {page_title} Smart Tag is rendered allow injected script to be reflected in a confirmation message. Exploitation is limited to confirmation messages in which an administrator has placed this Smart Tag within an HTML attribute context.
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.
The repository contains a README and two standalone proof-of-concept implementations: poc.py (Python standard library only) and poc.sh (Bash/curl). It targets an incomplete Smart Tag escaping fix in WPForms 2.0.2.1. The Python script fetches a supplied page, discovers WPForms form and post IDs plus form inputs, probes text fields with an event-handler payload, anonymously submits to the WordPress wpforms_submit AJAX action, and classifies returned confirmation occurrences as live attribute-name injection or escaped/inert output. It additionally submits a quote-breaking control payload to demonstrate that quoted attribute-value positions are escaped, then repeats the viable payload over the regular form POST path. The Bash PoC is a minimal local-rig variant for form ID 17 and field ID 3. Exploitation depends on a nondefault administrator-created confirmation template that uses a bare field Smart Tag where an HTML attribute name is expected; no server-side payload, persistence, authentication bypass, or shell capability is included.
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.