CVE-2022-2198

WPQA - Builder forms Addon For WordPress < 5.7 - Information Disclosure

2022-08-01 00:00
Bikram Kharal (themarkib)

Strategic Overview

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

At a glance

CVE-2022-2198 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WPQA - Builder forms Addon For WordPress WordPress plugin, affecting versions < 5.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The issue is fixed in version 5.7; sites on affected versions should update now. Disclosed August 2022, reported by Bikram Kharal (themarkib).

Vulnerability Overview

The WPQA Builder WordPress plugin before 5.7 which is a companion plugin to the Hilmer and Discy , does not check authorization before displaying private messages, allowing any logged in user to read other users private message using the message id, which can easily be brute forced.

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. A successful exploit has high impact on confidentiality.

CWE-639: Authorization Bypass Through User-Controlled Key

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

Remediation

Update to version 5.7, 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.7 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-2198https://www.wordfence.com/threat-intel/vulnerabilities/id/dd7b72bb-2cf7-4a8d-b323-66c94b500cb0https://nvd.nist.gov/vuln/detail/CVE-2022-2198

Related records

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