¿Es seguro Wp Optimize?

Qué hace este plugin

• Slug: wp-optimize
• 1000000+ instalaciones activas

cachecachingimage cacheminifyperformance cache

Estado de mantenimiento

• Última versión conocida: 4.6.0
• Requiere PHP: 7.2+
• PHP máximo soportado (analizado): <8.0

Vulnerabilidades conocidas

4 CVEs conocidos registrados para Wp Optimize.

CVE-2026-7252

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.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: CVE.org

CVE-2023-1119

Update the WordPress WP-Optimize plugin to the latest available version (at least 3.2.13). Paolo Elia discovered and reported this Cross Site Scripting (XSS) vulnerability in WordPress WP-Optimize Plugin. This could allow a malicious actor to inject malicious scripts, such as redirects, advertisements, and other HTML payloads into your website which will be executed when guests visit your site. This vulnerability has been fixed in version 3.2.13.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Patchstack

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance [wp-optimize] < 3.2.12

Update the WordPress WP-Optimize plugin to the latest available version (at least 3.2.12). Wordfence discovered and reported this Cross Site Request Forgery (CSRF) vulnerability in WordPress WP-Optimize Plugin. This could allow a malicious actor to force higher privileged users to execute unwanted actions under their current authentication. For example a password change which will then allow the malicious actor to login into the admin account. This vulnerability has been fixed in version 3.2.12.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Patchstack

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance [wp-optimize] < 3.2.12

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.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Wordfence

CVE-2025-3951

The WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 4.1.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Wordfence

CVE-2026-2712

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`).

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Wordfence

Cómo solucionarlo

Mantén Wp Optimize actualizado — 4.6.0 es la última versión en wordpress.org, y cada CVE de arriba indica la versión exacta que lo corrigió ("Corregido en").

Este es el historial completo de vulnerabilidades conocidas del plugin, no un escaneo de una instalación específica — ejecuta un escaneo gratis de tu propio sitio para verificar tu versión instalada exacta.

Alternativas más seguras / más establecidas

• LiteSpeed Cache — 7000000+ instalaciones activas — 96/100 (2761) — PHP máx. 8.4
• WP Super Cache — 1000000+ instalaciones activas — 86/100 (1343) — PHP máx. 8.4
• WP Fastest Cache – WordPress Cache Plugin — 1000000+ instalaciones activas — 98/100 (4220) — PHP máx. 8.4
• Speed Optimizer – The All-In-One Performance-Boosting Plugin — 1000000+ instalaciones activas — 84/100 (637) — PHP máx. 8.4
• W3 Total Cache — 900000+ instalaciones activas — 88/100 (5419)