CVE-2024-13338

Webcraftic Clearfy – WordPress optimization plugin <= 2.3.1 - Cross-Site Request Forgery to Clear Cache

2025-04-11 00:00
Whit Taylor

Strategic Overview

Status
Patched in 2.3.2
Affected Plugin
Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer
Affected Version
<= 2.3.1
CVSS
5.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-13338
View all Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer vulnerabilities

At a glance

CVE-2024-13338 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Clearfy Cache WordPress plugin, affecting versions <= 2.3.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.3.2; sites on affected versions should update now. Disclosed April 2025, reported by Whit Taylor.

Vulnerability Overview

The Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.3.1. This is due to missing or incorrect nonce validation on the wclearfy_cache_delete functionality . This makes it possible for unauthenticated attackers to clear the cache 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, and no interaction from a victim user.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Clearfy Cache <= 2.3.1 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 Clearfy Cache the fix is 2.3.2: builds <= 2.3.1 are affected, anything from 2.3.2 onward is not.

Remediation

Update to version 2.3.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Clearfy Cache: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Clearfy Cache 2.3.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-13338https://www.wordfence.com/threat-intel/vulnerabilities/id/e0a37ce4-9860-415e-bb88-545c30c95fc1https://nvd.nist.gov/vuln/detail/CVE-2024-13338

Related records

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