CVE-2025-13749 MEDIUM

CVE-2025-13749: Clearfy <= 2.4.0 - Cross-Site Request Forgery to Update Notification Tampering

Vendor Creativemotion
Product Clearfy Cache – WordPress optimization plugin, Minify HTML, CSS & JS, Defer
Weakness CWE-352 · CSRF
Published January 9, 2026
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.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.

Explanation of Vulnerability in Simple Terms

02Summary

Clearfy Cache versions up to 2.4.0 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 changes to plugin settings or site configuration. The vulnerability requires user interaction—the admin must click the link or visit the attacker's page while logged in.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unauthorized actions on the site via a malicious link or page.

Potential impact on your site

04Site Impact

An attacker could modify Clearfy Cache settings or trigger unintended site changes if an admin is tricked into clicking a malicious link.

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

January 9, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE