Clearfy <= 2.4.0 - Cross-Site Request Forgery to Update Notification Tampering
Strategic Overview
- Status
- Patched in 2.4.1
- Affected Version
<= 2.4.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-13749
At a glance
CVE-2025-13749 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Clearfy Cache WordPress plugin, affecting versions <= 2.4.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 2.4.1; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.
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.4.0. This is due to missing nonce validation on the "wbcr_upm_change_flag" function. This makes it possible for unauthenticated attackers to disable plugin/theme update notifications 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)
Clearfy Cache <= 2.4.0 carries this weakness at wbcr_upm_change_flag, 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 Clearfy Cache the fix is 2.4.1: builds <= 2.4.0 are affected, anything from 2.4.1 onward is not.
Remediation
Update to version 2.4.1, 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.4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer
- 7.2CVE-2026-3220: Multiple Plugins <= Multiple Versions Stored XSS
CVE-2026-3220 - 6.6CVE-2026-16297: Clearfy <= 2.4.2 PHP Object Injection
CVE-2026-16297 - 6.1Clearfy Cache <= 2.0.4 Reflected Cross-Site Scripting
- 4.3CVE-2026-16295: Clearfy Cache Information Exposure
CVE-2026-16295 - 4.3CVE-2024-43260: Clearfy Cache <= 2.2.4 Missing Authorization
CVE-2024-43260
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C