CVE-2024-2376

WPQA Builder <= 6.1.0 - Cross-Site Request Forgery

2024-06-12 00:00
Bob Matyas

Strategic Overview

Status
Patched in 6.1.1
Affected Plugin
WPQA - Builder forms Addon For WordPress
Affected Version
<= 6.1.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-2376
View all WPQA - Builder forms Addon For WordPress vulnerabilities

At a glance

CVE-2024-2376 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPQA - Builder forms Addon For WordPress WordPress plugin, affecting versions <= 6.1.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.1; sites on affected versions should update now. Disclosed June 2024, reported by Bob Matyas.

Vulnerability Overview

The WPQA Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.1.0. This is due to missing or incorrect nonce validation on several AJAX actions. This makes it possible for unauthenticated attackers to perform unauthorized actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WPQA - Builder forms Addon For WordPress <= 6.1.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPQA - Builder forms Addon For WordPress the fix is 6.1.1: builds <= 6.1.0 are affected, anything from 6.1.1 onward is not.

Remediation

Update to version 6.1.1, 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 6.1.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-2376https://www.wordfence.com/threat-intel/vulnerabilities/id/0e1d9c22-dcd3-47f9-aac0-c9626aa2821chttps://nvd.nist.gov/vuln/detail/CVE-2024-2376

Related records

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