CVE-2024-30518

Custom WooCommerce Checkout Fields Editor <= 1.3.0 - Cross-Site Request Forgery

2024-03-28 00:00
Skalucy

Strategic Overview

Status
Patched in 1.3.1
Affected Plugin
Custom WooCommerce Checkout Fields Editor
Affected Version
<= 1.3.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-30518
View all Custom WooCommerce Checkout Fields Editor vulnerabilities

At a glance

CVE-2024-30518 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Custom WooCommerce Checkout Fields Editor WordPress plugin, affecting versions <= 1.3.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 1.3.1; sites on affected versions should update now. Disclosed March 2024, reported by Skalucy.

Vulnerability Overview

The Custom WooCommerce Checkout Fields Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.0. This is due to missing or incorrect nonce validation. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 Custom WooCommerce Checkout Fields Editor <= 1.3.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 Custom WooCommerce Checkout Fields Editor the fix is 1.3.1: builds <= 1.3.0 are affected, anything from 1.3.1 onward is not.

Remediation

Update to version 1.3.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Custom WooCommerce Checkout Fields Editor: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Custom WooCommerce Checkout Fields Editor 1.3.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-30518https://www.wordfence.com/threat-intel/vulnerabilities/id/698c8c4e-77ca-491c-bdd5-4a3d3b99b1b4https://nvd.nist.gov/vuln/detail/CVE-2024-30518

Related records

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