WP-Optimize <= 4.5.0 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update and Image Manipulation
Strategic Overview
- Status
- Patched in 4.5.1
- Affected Plugin
- WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
- Affected Version
<= 4.5.0- CVSS
- 5.4Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-2712
At a glance
CVE-2026-2712 is a medium-severity Incorrect Authorization vulnerability in the WP-Optimize WordPress plugin, affecting versions <= 4.5.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.5.1; sites on affected versions should update now. Disclosed April 2026, reported by Dmitrii Ignatyev.
Vulnerability Overview
The WP-Optimize plugin for WordPress is vulnerable to unauthorized access of functionality due to missing capability checks in the `receive_heartbeat()` function in `includes/class-wp-optimize-heartbeat.php` in all versions up to, and including, 4.5.0. This is due to the Heartbeat handler directly invoking `Updraft_Smush_Manager_Commands` methods without verifying user capabilities, nonce tokens, or the allowed commands whitelist that the normal AJAX handler (`updraft_smush_ajax`) enforces. This makes it possible for authenticated attackers, with Subscriber-level access and above, to invoke admin-only Smush operations including reading log files (`get_smush_logs`), deleting all backup images (`clean_all_backup_images`), triggering bulk image processing (`process_bulk_smush`), and modifying Smush options (`update_smush_options`).
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 interaction from a victim user.
CWE-863: Incorrect Authorization
WP-Optimize <= 4.5.0 carries this weakness at receive_heartbeat(), and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For WP-Optimize the fix is 4.5.1: builds <= 4.5.0 are affected, anything from 4.5.1 onward is not.
Remediation
Update to version 4.5.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP-Optimize 4.5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C