CVE-2024-10593

WPForms – Easy Form Builder for WordPress <= 1.9.1.6 - Cross-Site Request Forgery (CSRF) to Plugin's Log Deletion

2024-11-12 14:02
Asaf Mozes

Strategic Overview

Status
Patched in 1.9.2.1
Affected Plugin
WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More
Affected Version
<= 1.9.1.6
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-10593
View all WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More vulnerabilities

At a glance

CVE-2024-10593 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPForms WordPress plugin, affecting versions <= 1.9.1.6. 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 1.9.2.1; sites on affected versions should update now. Disclosed November 2024, reported by Asaf Mozes.

Vulnerability Overview

The WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.1.6. This is due to missing or incorrect nonce validation on the process_admin_ui function. This makes it possible for unauthenticated attackers to delete WPForm logs 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 WPForms <= 1.9.1.6 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 WPForms the fix is 1.9.2.1: builds <= 1.9.1.6 are affected, anything from 1.9.2.1 onward is not.

Remediation

Update to version 1.9.2.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPForms: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPForms 1.9.2.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-10593https://www.wordfence.com/threat-intel/vulnerabilities/id/6d1ea80a-a1ce-4964-8dde-f3ed2df5537chttps://nvd.nist.gov/vuln/detail/CVE-2024-10593

Related records

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