CVE-2024-31924

EWWW Image Optimizer <= 7.2.3 - Cross-Site Request Forgery

2024-04-10 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 7.3.0
Affected Plugin
EWWW Image Optimizer
Affected Version
<= 7.2.3
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31924
View all EWWW Image Optimizer vulnerabilities

At a glance

CVE-2024-31924 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the EWWW Image Optimizer WordPress plugin, affecting versions <= 7.2.3. 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 7.3.0; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.

Vulnerability Overview

The EWWW Image Optimizer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.2.3. This is due to missing or incorrect nonce validation on the check_for_optin() and check_for_optout() functions. This makes it possible for unauthenticated attackers to opt in and out of tracking 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)

EWWW Image Optimizer <= 7.2.3 carries this weakness at check_for_optin(), 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 EWWW Image Optimizer the fix is 7.3.0: builds <= 7.2.3 are affected, anything from 7.3.0 onward is not.

Remediation

Update to version 7.3.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31924https://www.wordfence.com/threat-intel/vulnerabilities/id/074d7b46-60e0-4d4a-904a-696ac7948a35https://nvd.nist.gov/vuln/detail/CVE-2024-31924

Related records

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