sales@hackhalt.com

Home / Threats / CVE-2026-91051

EWWW Image Optimizer - Security Vulnerability (CVE-2026-91051)

CVE-2026-91051

The EWWW Image Optimizer WordPress plugin before 8.8.0 does not prevent authenticated users with author-level permissions from storing a serialized value in a post meta field that is deserialized when the post is rendered, allowing them to perform PHP Object Injection, which can lead to remote code execution when a suitable gadget chain is present via another installed EWWW Image Optimizer WordPress plugin before 8.8.0 or .

CVE-2026-91051

MEDIUM CVSS 6.6 Published 2026-09-30 Updated 2026-09-30
AI Risk Elevated (65/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine Elevated (65/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-30 CVE published and first recorded in the threat feed.
  2. 2026-09-30 Record updated with latest vulnerability metadata.
  3. 2026-10-02 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 45 days ago

AI enriched 45 days ago (2026-10-02 08:00 UTC)

Technical Summary

The EWWW Image Optimizer WordPress plugin before 8.8.0 does not prevent authenticated users with author-level permissions from storing a serialized value in a post meta field that is deserialized when the post is rendered, allowing them to perform PHP Object Injection, which can lead to remote code execution when a suitable gadget chain is present via another installed EWWW Image Optimizer WordPress plugin before 8.8.0 or .

Potential Impact

Severity is MEDIUM (CVSS 6.6). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 65/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

EWWW Image Optimizer PLUGIN · ewww-image-optimizer Affected: < 8.8.0 Fixed in: 8.8.0

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update EWWW Image Optimizer to 8.8.0 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs EWWW Image Optimizer, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs EWWW Image Optimizer. Versions below 8.8.0 are vulnerable; that release and later are not.

How do I fix it?

Update EWWW Image Optimizer to version 8.8.0 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Remote Code Execution flaw. An attacker who exploits it can run their own code on the server, which is total control of the site.