WP-Optimize <= 3.2.11 - Cross-Site Request Forgery

2023-02-06 00:00
Anonymous

Strategic Overview

Status
Patched in 3.2.12
Affected Plugin
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
Affected Version
<= 3.2.11
CVSS
6.5Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP-Optimize WordPress plugin, affecting versions <= 3.2.11. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.2.12; sites on affected versions should update now. Disclosed February 2023.

Vulnerability Overview

The WP-Optimize plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.11. This is due to missing or incorrect nonce validation on the 'is_valid_request' function. This makes it possible for unauthenticated attackers to manage and modify cache and minification settings and dismiss 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. A successful exploit has high impact on integrity.

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

WP-Optimize <= 3.2.11 carries this weakness at is_valid_request, 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 WP-Optimize the fix is 3.2.12: builds <= 3.2.11 are affected, anything from 3.2.12 onward is not.

Remediation

Update to version 3.2.12, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/c3190f9f-8b2f-4251-8804-f386e2c5678f

Related records

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