CVE-2022-1051

WPQA - Builder forms Addon For WordPress < 5.2 - Stored Cross-Site Scripting via Profile fields

2022-04-21 00:00
Veshraj Ghimire

Strategic Overview

Status
Patched in 5.2
Affected Version
< 5.2
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-1051
View all WPQA - Builder forms Addon For WordPress vulnerabilities

At a glance

CVE-2022-1051 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WPQA - Builder forms Addon For WordPress WordPress plugin, affecting versions < 5.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 5.2; sites on affected versions should update now. Disclosed April 2022, reported by Veshraj Ghimire.

Vulnerability Overview

The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not sanitise and escape the city, phone or profile credentials fields when outputting it in the profile page, allowing any authenticated user to perform Cross-Site Scripting attacks.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.

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

Reaching this weakness in WPQA - Builder forms Addon For WordPress < 5.2 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 WPQA - Builder forms Addon For WordPress the fix is 5.2: builds < 5.2 are affected, anything from 5.2 onward is not.

Remediation

Update to version 5.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPQA - Builder forms Addon For WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPQA - Builder forms Addon For WordPress 5.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