Skip to main content
VulnerabilityPublished

CVE-2026-124969: Optimole (WordPress plugin) · Deserialization of Untrusted Data

Affects Optimole (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 14 Nov 2026, 05:04 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
optimoleOptimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image OptimizationAffected
  • <=4.2.19
Fixed in–

AI-suggested

Users should monitor vendor advisories for updates. Until a fix is available, restrict access to the plugin's administrative functions and ensure that the PEAR Archive_Tar library is not unnecessarily installed or accessible. Administrators should be cautious when using the plugin's Rename control on attachments, especially if suspicious comments or payloads are present.

Description

The Optimole WordPress plugin up to version 4.2.19 contains a vulnerability that allows unauthenticated attackers to delete arbitrary files on the server due to insufficient file path validation. Exploitation requires the presence of PEAR's Archive_Tar library and an administrator to perform a rename action on an attachment after the attacker stages a malicious payload in a comment. This can lead to remote code execution if critical files like wp-config.php are deleted.

References

Community reviews

Loading reviews…