Breeze <= 2.0.8 - Cross-Site Request Forgery via import_json_settings

2022-09-19 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.9
Affected Plugin
Breeze Cache
Affected Version
<= 2.0.8
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Breeze Cache vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Breeze Cache WordPress plugin, affecting versions <= 2.0.8. 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.0.9; sites on affected versions should update now. Disclosed September 2022.

Vulnerability Overview

The Breeze plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.8. This is due to missing or incorrect nonce validation on the 'import_json_settings' function. This makes it possible for unauthenticated attackers to import plugin settings 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)

Breeze Cache <= 2.0.8 carries this weakness at import_json_settings, 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 Breeze Cache the fix is 2.0.9: builds <= 2.0.8 are affected, anything from 2.0.9 onward is not.

Remediation

Update to version 2.0.9, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/80192348-dcf4-4bab-80d1-ae7a4d194270

Related records

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