Skip to main content
VulnerabilityPublished

CVE-2026-92826: EWWW Image Optimizer (WordPress plugin) · Cross-site Scripting

Affects EWWW Image Optimizer (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 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 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
nosilver4uEWWW Image OptimizerAffected
  • <=8.7.7
Fixed in–

AI-suggested

Users should verify the status of the 'enable_help' option and consider disabling it to prevent the vulnerable script block from being emitted. Monitor vendor advisories for updates or patches addressing this vulnerability. Until a fix is available, restricting or sanitizing inputs related to REQUEST_URI parameters may reduce risk.

Description

The EWWW Image Optimizer plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via REQUEST_URI Parameter Key in all versions up to, and including, 8.7.7 due to insufficient input sanitization and output escaping. 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. Successful exploitation requires that the enable_help option is active, as the vulnerable HelpScout Beacon script block is only emitted when that setting is enabled.

References

Community reviews

Loading reviews…