CVE-2026-124969

validatedZero produced an exploit or a check.

GHSA-9367-hx9q-rjcg ↗EUVD-2026-125850 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization <= 4.2.19
CWE-502 Deserialization of Untrusted Data
ETK-2026-4444Zero's internal tracking ID, independent of the CVE number., permanent identifier
+26mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+26magent stopped
0
+5min
+10min
+15min
+20min

description

Optimole for WordPress through version 4.2.19 can allow an unauthenticated attacker to cause deletion of files on the server. Exploitation requires PEAR Archive_Tar to be available and an administrator to later use the plugin’s Rename control after malicious content has been placed in a comment; file deletion may enable further compromise.

mitigation

Disable the Optimole plugin or restrict its use of the Rename control until a vendor-fixed release is available. Remove or limit access to PEAR Archive_Tar where operationally feasible, and review comments and administrative media actions for suspicious activity.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-14 04:46Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

this entry in the feed

GET /api/v1/feed/CVE-2026-124969

{
  "etk_id": "ETK-2026-4444",
  "cve_id": "CVE-2026-124969",
  "display_id": "CVE-2026-124969",
  "ghsa_id": "GHSA-9367-hx9q-rjcg",
  "euvd_id": "EUVD-2026-125850",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file deletion in Optimole for WordPress",
  "summary": "Optimole for WordPress through version 4.2.19 can allow an unauthenticated attacker to cause deletion of files on the server. Exploitation requires PEAR Archive_Tar to be available and an administrator to later use the plugin’s Rename control after malicious content has been placed in a comment; file deletion may enable further compromise.",
  "mitigation": "Disable the Optimole plugin or restrict its use of the Rename control until a vendor-fixed release is available. Remove or limit access to PEAR Archive_Tar where operationally feasible, and review comments and administrative media actions for suspicious activity.",
  "vendor": "optimole",
  "product": "Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.2.19"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.008969333333333333,
  "t0_at": "2026-11-14T04:46:10.600000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-14T05:12:17.873084+00:00",
      "days": 0.018139734768518517,
      "is_lower_bound": false,
      "measured_at": "2026-11-14T04:46:10.600000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-14T04:46:10.600000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-14T04:46:10.600000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124969"
    }
  }
}

published 2026-11-14 05:11Z
last change 2026-11-14 07:41Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.