CVE-2024-13337 MEDIUM

CVE-2024-13337: Webcraftic Clearfy – WordPress optimization plugin <= 2.3.2 - Cross-Site Request Forgery to Plugin Settings Update via 'setup-wbcr_clearfy'

Vendor Creativemotion
Product Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer
Weakness CWE-352 · CSRF
Published April 12, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.2. This is due to missing or incorrect nonce validation on the 'setup-wbcr_clearfy' page. This makes it possible for unauthenticated attackers to update the plugins settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

Clearfy Cache versions up to 2.3.2 contain a cross-site request forgery (CSRF) vulnerability that allows attackers to perform unauthorized actions on behalf of site administrators. An attacker can craft a malicious link or page that, when visited by an admin, triggers unwanted plugin configuration changes or other administrative operations. The vulnerability requires user interaction—the admin must click the link or visit the attacker's page—but no authentication is needed from the attacker's side.

What an attacker can do

03Attacker Capabilities

Trick a site admin into performing unauthorized plugin actions by visiting a malicious link.

Potential impact on your site

04Site Impact

Plugin settings could be altered without your knowledge if you click a suspicious link while logged in.

Conditions required to exploit

05Prerequisites

Admin must click a malicious link or visit an attacker-controlled page while logged into WordPress.

Key dates

06Disclosure timeline

April 12, 2025 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE