HomeWordPress vulnerabilitiesWP-Optimize
WP-Optimize vulnerabilities
WP-Optimize has 4 known vulnerabilities in this database. The most recent published record is dated 7 May 2026.
- Known vulnerabilities
- 4
- Active installs
- 1m+
- Latest version
- 4.7.0
- Last updated
- 21 Sep 2026
- Most recent
- 7 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-7252 | High 8.1 | Up to 4.5.2 | Fixed in a later version (latest 4.7.0) | 7 May 2026 |
| Broken access control CVE-2026-2712 | Medium 5.4 | Up to 4.5.0 | Fixed in a later version (latest 4.7.0) | 10 Apr 2026 |
| SQL injection CVE-2025-3951 | Medium 4.1 | Before 4.2.0 | Fixed in 4.2.0 | 2 Jun 2025 |
| Cross-site scripting (XSS) CVE-2023-1119 | Medium 6.1 | Before 3.2.13 | Fixed in 3.2.13 | 10 Jul 2023 |
Read the published descriptions
- CVE-2026-7252, 7 May 2026
- The WP-Optimize - Cache, Compress images, Minify & Clean database to boost page speed & performance plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unscheduled_original_file_deletion function in all versions up to, and including, 4.5.2 This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This is possible because 'original-file' is a public (non-protected) meta key - it does not begin with an underscore - allowing Authors to freely create or modify it on their own attachment posts via the standard Edit Media form or the REST API. CVE record
- CVE-2026-2712, 10 Apr 2026
- 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`). CVE record
- CVE-2025-3951, 2 Jun 2025
- The WP-Optimize WordPress plugin before 4.2.0 does not properly escape user input when checking image compression statuses, which could allow users with the administrator role to conduct SQL Injection attacks in the context of Multi-Site WordPress configurations. CVE record
- CVE-2023-1119, 10 Jul 2023
- The WP-Optimize WordPress plugin before 3.2.13, SrbTransLatin WordPress plugin before 2.4.1 use a third-party library that removes the escaping on some HTML characters, leading to a cross-site scripting vulnerability. CVE record
What to do if you run WP-Optimize
If you run WP-Optimize, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP-Optimize vulnerabilities
Free. We email you when a new vulnerability is published for WP-Optimize, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.