Skip to main content
Menu
CVEs

Optimole Optimize Images unauthenticated stored XSS via comment body

CVE-2026-125094EUVD-2026-131498GHSA-WMJ2-RXC5-87QGPublished , updated

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Optimole plugin for WordPress has a stored cross-site scripting flaw in its comment handling. Attackers can reach it remotely, without logging in. They can inject scripts into pages that run in the browser of any user who opens an affected page, provided the AMP plugin is active in Transitional or Standard mode and comments are open on the post.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125094 (Optimole <= 4.2.19 - Unauthenticated Stored Cross-Site Scripting via Comment body), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125094 (entry last updated 2026-11-20):
Affected:
- optimole Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization: through 4.2.19
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125094 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125094 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/3d017da6-553a-4e6e-8a8c-8ec7eda0ed7a?source=cve
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.19/inc/admin.php#L520
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.19/inc/v2/BgOptimizer/Lazyload.php#L15
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.19/inc/v2/BgOptimizer/Lazyload.php#L132
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.19/inc/manager.php#L593
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.19/inc/rest.php#L184
- https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.20
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125094
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125094"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 9

Questions about CVE-2026-125094

Is CVE-2026-125094 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-125094?

Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization: through 4.2.19.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.