CVE-2024-30456

WPCS <= 1.2.0.1 - Cross-Site Request Forgery

2024-03-28 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 1.2.0.2
Affected Plugin
WPCS – WordPress Currency Switcher Professional
Affected Version
<= 1.2.0.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-30456
View all WPCS – WordPress Currency Switcher Professional vulnerabilities

At a glance

CVE-2024-30456 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPCS WordPress plugin, affecting versions <= 1.2.0.1. 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.2.0.2; sites on affected versions should update now. Disclosed March 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The WPCS plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.0.1. This is due to missing or incorrect nonce validation on the save_etalon() function. This makes it possible for unauthenticated attackers to update the plugin's settings 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)

WPCS <= 1.2.0.1 carries this weakness at save_etalon(), and reaching it 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 WPCS the fix is 1.2.0.2: builds <= 1.2.0.1 are affected, anything from 1.2.0.2 onward is not.

Remediation

Update to version 1.2.0.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPCS: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPCS 1.2.0.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-30456https://www.wordfence.com/threat-intel/vulnerabilities/id/2227cde8-5ed6-44dd-80cc-2a85aaa172c1https://nvd.nist.gov/vuln/detail/CVE-2024-30456

Related records

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