HomeWordPress vulnerabilitiesOptimole
Optimole vulnerabilities
Optimole has 15 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.
- Known vulnerabilities
- 15
- Active installs
- 200,000+
- Latest version
- 4.2.19
- Last updated
- 4 Nov 2026
- Most recent
- 20 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
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 |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-125094 | High 7.2 | Up to 4.2.19 | No fixed version yet | 2 d ago |
| Remote code execution CVE-2026-124969 | High 7.1 | Up to 4.2.19 | No fixed version yet | 8 d ago |
| Cross-site scripting (XSS) CVE-2026-120677 | High 7.2 | Up to 4.2.18 | Fixed in a later version (latest 4.2.19) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-120739 | High 7.2 | Up to 4.2.18 | Fixed in a later version (latest 4.2.19) | 7 Nov 2026 |
| Cross-site scripting (XSS) CVE-2026-119070 | High 7.2 | Up to 4.2.17 | Fixed in a later version (latest 4.2.19) | 7 Nov 2026 |
| Sensitive data exposure CVE-2026-96530 | Medium 6.5 | Before 4.2.15 | Fixed in 4.2.15 | 7 Oct 2026 |
| Broken access control CVE-2026-102375 | Medium 6.5 | Up to 4.2.14 | Fixed in a later version (latest 4.2.19) | 30 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-96531 | Medium 6.8 | Before 4.2.13 | Fixed in 4.2.13 | 26 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-84829 | High 8.8 | Before 4.2.12 | Fixed in 4.2.12 | 16 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-77365 | High 7.2 | Up to 4.2.10 | Fixed in a later version (latest 4.2.19) | 28 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2026-11784 | Medium 4.3 | Up to 4.2.6 | Fixed in a later version (latest 4.2.19) | 18 Jun 2026 |
| Cross-site scripting (XSS) CVE-2026-5226 | Medium 6.1 | Up to 4.2.3 | Fixed in a later version (latest 4.2.19) | 11 Apr 2026 |
| Cross-site scripting (XSS) CVE-2026-5217 | High 7.2 | Up to 4.2.2 | Fixed in a later version (latest 4.2.19) | 11 Apr 2026 |
| Broken access control CVE-2025-11519 | Medium 4.3 | Up to 4.1.0 | Fixed in a later version (latest 4.2.19) | 18 Oct 2025 |
| Cross-site scripting (XSS) CVE-2024-4636 | Medium 6.4 | Up to 3.12.10 | Fixed in a later version (latest 4.2.19) | 15 May 2024 |
Read the published descriptions
- CVE-2026-125094, 20 Nov 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.19 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the AMP plugin to be active in Transitional or Standard template mode, and comments must be open on the target post, which is the WordPress default. CVE record
- CVE-2026-124969, 14 Nov 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the replace_urls_in_value function in all versions up to, and including, 4.2.19. This makes it possible for unauthenticated attackers 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). Successful exploitation requires PEAR's Archive_Tar library to be present and loadable on the host (common in official WordPress Docker images and many PHP distributions), and an administrator must subsequently use the plugin's Rename control on any attachment after the attacker has staged a malicious payload in a comment. Successful exploitation additionally requires an action by an administrator - the attacker cannot trigger the vulnerability on their own. CVE record
- CVE-2026-120677, 7 Nov 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.18 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the comment to be approved by an administrator and for the affected post to contain at least one iframe or video element (e.g., a core Video block), which is sufficient under default plugin settings where video lazy loading is enabled. CVE record
- CVE-2026-120739, 7 Nov 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 's (missing_srcsets[*][*].s)' parameter in all versions up to, and including, 4.2.18 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The HMAC signature required to pass the REST endpoint's authorization check is published in plaintext to unauthenticated visitors inside the inline optimoleDataOptimizer JavaScript object on any page with an incomplete profile, making the effective authentication barrier nonexistent. CVE record
- CVE-2026-119070, 7 Nov 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.17 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit requires the plugin to be in its normal connected state (cdn_key and cdn_secret configured) with the image replacer enabled, which is the default post-setup configuration; the stored payload bypasses all WordPress comment sanitization filters because it contains no HTML metacharacters at storage time - the characters are produced only by Optimole's own decoder at render time. CVE record
- CVE-2026-96530, 7 Oct 2026
- The Optimole WordPress plugin before 4.2.15 does not perform a capability check before exposing its stored image-optimization account data in a dashboard widget, allowing any authenticated user, including Subscribers, to read the site's third-party service credentials. CVE record
- CVE-2026-102375, 30 Sep 2026
- Missing Authorization vulnerability in Optimole Optimole optimole-wp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Optimole: from n/a through 4.2.14. CVE record
- CVE-2026-96531, 26 Sep 2026
- The Optimole WordPress plugin before 4.2.13 does not escape unrecognized attributes of its video-player block before rendering them onto the block's wrapper element, allowing users with the Author role and above to store an event-handler attribute that executes scripts in the browser of any user, such as an administrator, who views the post. CVE record
- CVE-2026-84829, 16 Sep 2026
- The Optimole WordPress plugin before 4.2.12 does not properly escape a user supplied value before using it to build an image tag attribute, allowing unauthenticated users to inject arbitrary attributes into pages served to every visitor, which leads to Stored Cross-Site Scripting. CVE record
- CVE-2026-77365, 28 Aug 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'a' (above_fold_images) parameter in all versions up to, and including, 4.2.10 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-11784, 18 Jun 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.6. This is due to missing or incorrect nonce validation on the replace_file function. This makes it possible for unauthenticated attackers to overwrite existing media attachments with attacker-supplied file content by supplying a forged multipart POST request targeting any attachment the victim has edit_post capability over via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The forged request requires a victim with at least Author-level privileges, as the handler enforces a current_user_can('edit_post', $id) check; tricking an Author-level or higher user into clicking a crafted link is sufficient to trigger the overwrite against attachments that user can edit. CVE record
- CVE-2026-5226, 11 Apr 2026
- The Optimole - Optimize Images in Real Time plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via URL paths in versions up to, and including, 4.2.3 This is due to insufficient output escaping on user-supplied URL paths in the get_current_url() function, which are inserted into JavaScript code via str_replace() without proper JavaScript context escaping in the replace_content() function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
- CVE-2026-5217, 11 Apr 2026
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.2.2. This is due to insufficient input sanitization and output escaping on the user-supplied 's' parameter (srcset descriptor) in the unauthenticated /wp-json/optimole/v1/optimizations REST endpoint. The endpoint validates requests using an HMAC signature and timestamp, but these values are exposed directly in the frontend HTML making them accessible to any visitor. The plugin uses sanitize_text_field() on the descriptor value of rest.php, which strips HTML tags but does not escape double quotes. The poisoned descriptor is then stored via transients (backed by the WordPress options table) and later retrieved and injected verbatim into the srcset attribute of tag_replacer.php without proper escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts into pages that will execute whenever a user accesses the injected page. CVE record
- CVE-2025-11519, 18 Oct 2025
- The Optimole - Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.1.0 via the /wp-json/optml/v1/move_image REST API endpoint due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to offload media that doesn't belong to them. CVE record
- CVE-2024-4636, 15 May 2024
- The Image Optimization by Optimole - Lazy Load, CDN, Convert WebP & AVIF plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘allow_meme_types’ function in versions up to, and including, 3.12.10 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run Optimole
If you run Optimole, 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 Optimole vulnerabilities
Free. We email you when a new vulnerability is published for Optimole, 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.