CVE-2026-101921

WPForms <= 2.0.2.1 - Reflected Cross-Site Scripting via 'query_var' Smart Tag in iframe srcdoc Attribute

2026-10-09 19:10
UKO

Strategic Overview

Status
Patched in 2.0.2.2
Affected Version
<= 2.0.2.1
CVSS
4.7Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2026-101921
View all WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More vulnerabilities

At a glance

CVE-2026-101921 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPForms WordPress plugin, affecting versions <= 2.0.2.1. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.0.2.2; sites on affected versions should update now. Disclosed October 2026, reported by UKO.

Vulnerability Overview

The WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'attacker-chosen key referenced by the smart tag (e.g. "x")' parameter in all versions up to, and including, 2.0.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Exploitation requires that a site administrator has previously saved a form whose description embeds a {query_var} Smart Tag inside an iframe srcdoc attribute and has enabled Show Description on a public-facing page.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WPForms <= 2.0.2.1 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WPForms the fix is 2.0.2.2: builds <= 2.0.2.1 are affected, anything from 2.0.2.2 onward is not.

Remediation

Update to version 2.0.2.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPForms: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPForms 2.0.2.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C