CVE-2022-1425

WPQA - Builder forms Addon For WordPress < 5.2 - Insecure Direct Object Reference to Private Message Disclosure

2022-04-21 00:00
Veshraj Ghimire

Strategic Overview

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

At a glance

CVE-2022-1425 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WPQA - Builder forms Addon For WordPress WordPress plugin, affecting versions < 5.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. 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 validate that the message_id of the wpqa_message_view ajax action belongs to the requesting user, leading to any user being able to read messages for any other users via a Insecure Direct Object Reference (IDOR) vulnerability.

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 privileges on the target site, 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.2 takes a caller who can reach the endpoint. 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.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?

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.2 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-1425https://www.wordfence.com/threat-intel/vulnerabilities/id/56036bb2-3af3-4f69-ab79-78c5bb266231https://nvd.nist.gov/vuln/detail/CVE-2022-1425

Related records

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