CVE-2022-3343

WPQA - Builder forms Addon For WordPress (<= 5.9.2), Himer (<= 1.9.3) and Discy (<= 5.5.3) - Authenticated (Subscriber+) Insecure Direct Object Reference

2022-12-13 00:00
Harsh Tandel

Strategic Overview

Status
Patched in 5.9.3
Affected Plugin
WPQA - Builder forms Addon For WordPress
Affected Version
<= 5.9.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-3343
View all WPQA - Builder forms Addon For WordPress vulnerabilities

At a glance

CVE-2022-3343 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WPQA - Builder forms Addon For WordPress WordPress plugin, affecting versions <= 5.9.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.9.3; sites on affected versions should update now. Disclosed December 2022, reported by Harsh Tandel.

Vulnerability Overview

The WPQA - Builder forms Addon For WordPress plugin is vulnerable to insecure direct object reference in versions up to, and including, 5.9.2 along with the Himer (<= 1.9.3) and Discy (<= 5.5.3) WordPress themes. This is due to insufficient validation of user follows on the wpqa_following_you_ajax action. This makes it possible for authenticated attackers with subscriber-level capabilities and above to inflate follower counts of others by sending repeat follow requests.

Technical Analysis

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

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WPQA - Builder forms Addon For WordPress <= 5.9.2 takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WPQA - Builder forms Addon For WordPress the fix is 5.9.3: builds <= 5.9.2 are affected, anything from 5.9.3 onward is not.

Remediation

Update to version 5.9.3, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPQA - Builder forms Addon For WordPress 5.9.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3343https://www.wordfence.com/threat-intel/vulnerabilities/id/085da0fa-9487-4938-94ea-c1593be7c023https://nvd.nist.gov/vuln/detail/CVE-2022-3343

Related records

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