CVE-2024-0374

Views for WPForms <= 3.2.2 - Cross-Site Request Forgery via create_view

2024-01-24 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 3.2.3
Affected Version
<= 3.2.2
CVSS
4.3Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-0374
View all Views for WPForms – Display & Edit WPForms Entries on your site frontend vulnerabilities

At a glance

CVE-2024-0374 is a medium-severity Improper Access Control vulnerability in the Views for WPForms WordPress plugin, affecting versions <= 3.2.2. 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 3.2.3; sites on affected versions should update now. Disclosed January 2024, reported by Francesco Carlucci.

Vulnerability Overview

The Views for WPForms – Display & Edit WPForms Entries on your site frontend plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.2. This is due to missing or incorrect nonce validation on the 'create_view' function. This makes it possible for unauthenticated attackers to create views 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-284: Improper Access Control

Views for WPForms <= 3.2.2 carries this weakness at create_view, and reaching it takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Views for WPForms the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.

Remediation

Update to version 3.2.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: Views for WPForms 3.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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