Answer in brief
CVE-2026-124969 records a High severity (CVSS 7.1) vulnerability in Optimole <= 4.2.19 - Unauthenticated PHP Object Injection to Arbitrary File Deletion via 'comment_content'/'comment_agent' Parameter during Attachment Rename. The current sources do not mark it as known exploited. The current feed maps optimole/Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps optimole/Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| optimole/Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimizationgeneric | >=0 <=4.2.19 | Not reported |
Published upstream
Nov 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 14, 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.
Quoted source text, attributed separately from HOL analysis.