EWWW Image Optimizer vulnerability history, read beside its compression and WebP settings
EWWW Image Optimizer compresses uploads on your own web server or through its vendor's Compress API, and two of its WebP delivery methods change a page's image URLs or markup.
These are the records the source data files for it, and where to read its mode, delivery method, hourly schedule and Media Library links.
On this page
EWWW Image Optimizer vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 15 records for EWWW Image Optimizer. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 8.9.2
Worked out from data retrieved on .
Every affected range listed in this source for EWWW Image Optimizer ends before version 8.9.2.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
EWWW Image Optimizer <= 8.9.1 - Unauthenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-124254
Affected versions- All versions up to and including 8.9.1
Patched versions: 8.9.2
Update to at least version 8.9.2.
EWWW Image Optimizer 8.7.4 - 8.9.0 - Authenticated (Author+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-91049
Affected versions- From version 8.7.4 up to and including 8.9.0
Patched versions: 8.9.1
Update to at least version 8.9.1.
EWWW Image Optimizer <= 8.7.7 - Reflected Cross-Site Scripting via REQUEST_URI Parameter Key
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2026-92826
Affected versions- All versions up to and including 8.7.7
Patched versions: 8.8.0
Update to at least version 8.8.0.
EWWW Image Optimizer <= 8.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-97067
Affected versions- All versions up to and including 8.7.7
Patched versions: 8.8.0
Update to at least version 8.8.0.
EWWW Image Optimizer 8.6.0 - 8.7.7 - Authenticated (Author+) PHP Object Injection
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2026-91051
Affected versions- From version 8.6.0 up to and including 8.7.7
Patched versions: 8.8.0
Update to at least version 8.8.0.
Show 10 older recordsHide the older records
EWWW Image Optimizer <= 8.7.0 - Authenticated (Administrator+) Cross-Site WebP File Deletion or Rename
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.7)
- CVE:
- CVE-2026-91072
Affected versions- All versions up to and including 8.7.0
Patched versions: 8.8.0
Update to at least version 8.8.0.
EWWW Image Optimizer <= 8.7.6 - Authenticated (Author+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-91011
Affected versions- All versions up to and including 8.7.6
Patched versions: 8.7.7
Update to at least version 8.7.7.
EWWW Image Optimizer <= 8.7.6 - Unauthenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-84773
Affected versions- All versions up to and including 8.7.6
Patched versions: 8.7.7
Update to at least version 8.7.7.
EWWW Image Optimizer <= 8.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post Content
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-15446
Affected versions- All versions up to and including 8.7.3
Patched versions: 8.7.4
Update to at least version 8.7.4.
EWWW Image Optimizer <= 7.2.3 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2024-31924
Affected versions- All versions up to and including 7.2.3
Patched versions: 7.3.0
Update to at least version 7.3.0.
EWWW Image Optimizer <= 7.2.0 - Unauthenticated Sensitive Information Exposure via Debug Log
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2023-40600
Affected versions- All versions up to and including 7.2.0
Patched versions: 7.2.1
Update to at least version 7.2.1.
EWWW Image Optimizer <= 7.2.0 - Sensitive Information Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions- All versions before 7.2.1
Patched versions: 7.2.1
Update to at least version 7.2.1.
EWWW Image Optimizer <= 5.8.1 - Cross-Site Request Forgery Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2020-36750
Affected versions- All versions up to and including 5.8.1
Patched versions: 5.9
Update to at least version 5.9.
EWWW Image Optimizer <= 2.8.4 - Remote Code Execution
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.6)
- CVE:
- CVE-2016-20010
Affected versions- All versions up to and including 2.8.4
Patched versions: 2.8.5
Update to at least version 2.8.5.
EWWW Image Optimizer <= 2.0.1 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2014-6243
Affected versions- All versions up to and including 2.0.1
Patched versions: 2.0.2
Update to at least version 2.0.2.
Check EWWW Image Optimizer on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What EWWW Image Optimizer does with images, and who reaches it
EWWW Image Optimizer is an image compression plugin, shown on WordPress.org as "By Shane Bishop".
Its listing says it works "using tools on your own web server (jpegtran, optipng, pngout, pngquant, gifsicle, cwebp)", that this requires the PHP exec() function and a compatible web server, and that where a web server is not compatible the vendor offers lossless JPG compression and WebP conversion through its Compress API.
Start with two of the ways content reaches it. The vendor's How to use article says it automatically optimises any images uploaded to the Media Library, and WordPress documents an Author as holding the upload_files capability and a Contributor as not holding it.
The other way is the page a visitor loads: the vendor's WebP Delivery article says JS WebP Rewriting uses JavaScript to change image URLs and that <picture> WebP Rewriting wraps images inside an HTML picture element.
Settings have a second home: the Override Options article says any of them can be overridden by a constant defined in wp-config.php.
Three ways to misread the EWWW Image Optimizer vulnerabilities
The phrase Stored Cross-Site Scripting recurs through the titles in this history, behind access wording that differs between titles: Unauthenticated, Authenticated (Contributor+), Authenticated (Author+).
Three things here are easy to misread.
Records that share a title ending
CVE-2026-91011 and CVE-2026-91049 both have a title ending "Authenticated (Author+) Stored Cross-Site Scripting". The first gives its affected range as all versions up to and including 8.7.6 and lists 8.7.7 as patched. The second gives from version 8.7.4 up to and including 8.9.0 and lists 8.9.1. Match on the CVE id and the fields: a copy at the first record's patched version sits inside the second record's range.
Some ranges start partway through
CVE-2026-91051, whose title ends "Authenticated (Author+) PHP Object Injection", runs from version 8.6.0 up to and including 8.7.7, with 8.8.0 in its patched versions field. A copy older than 8.6.0 is outside that record and inside others: CVE-2026-15446, whose title ends "Authenticated (Contributor+) Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post Content", gives all versions up to and including 8.7.3 and lists 8.7.4.
A patched version past the end of its range
CVE-2026-91072 has a title ending "Authenticated (Administrator+) Cross-Site WebP File Deletion or Rename". Its affected range is all versions up to and including 8.7.0 and its patched versions field lists 8.8.0. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
Before relying on the update guidance at the top of the history, read the changelog on the plugin's WordPress.org listing too. It is the vendor's own account of each release, some of its lines begin with the word security, and a release it describes may have no record on this page.
Where each EWWW Image Optimizer check is read
These checks read and record; none changes a setting.
The plugin's screens spell optimise with a z, so this page describes those controls and does not quote their labels. Opening the settings page is not passive: the vendor's article on background mode says every visit to the EWWW IO settings should automatically re-test background mode, a test it describes as an HTTP request sent from the server to itself.
Press nothing there: the vendor's articles name a Re-test link, a button that starts the bulk process for local images and a one-click button that modifies the rewrite rules in .htaccess.
The WordPress Plugins screen gives each plugin's version number in its Description column. Write down the one for EWWW Image Optimizer, the date, and what the Automatic update column shows. Check the same list for a second copy: the vendor's article on which version to use says there used to be two versions, the regular one and a "cloud" version, and that the old Cloud edition will no longer receive updates and has been closed.
The listing's FAQ sets free mode using local server compression beside the Compress API and the Easy IO CDN. Record which the site uses and whether an API key is entered: the vendor's Local Compression Options article says that with a key, GIF files are processed via the API and all SVG optimisation is performed on the API servers.
It says the level options for each format are available by enabling Ludicrous Mode, which the Basic Configuration article says is reached by a link at the top of the Basic Settings.
Where a site is still in the basic view, note that and read the levels on a staging copy, so the mode is not enabled on the live site for this check.
Then read wp-config.php for constants beginning EWWW_IMAGE_OPTIMIZER_. The Override Options article lists settings "hidden from the settings page", among them EWWW_IMAGE_OPTIMIZER_NOAUTO, which turns off automatic optimisation when set to true.
Record whether WebP conversion is on and which method delivers the copies. The vendor's WebP Delivery article lists three in the plugin: Apache/Litespeed rewrite rules in .htaccess, JS WebP Rewriting and <picture> WebP Rewriting. Its Getting Started with WebP Images article adds that a site with the Easy IO CDN enabled does not need any other WebP options. For rewrite rules, read .htaccess itself.
From outside, the WebP Delivery article says server-based delivery leaves image URLs unchanged while the content type shows as WebP, and that the HTML-based methods change the URLs but the server may not know what a WebP image is; in that case it says the file extension is the confirmation and the content type the browser displays can be ignored. Note any domains listed for JS WebP, on the settings page or in the constant EWWW_IMAGE_OPTIMIZER_WEBP_PATHS.
The Advanced Configuration article says its options are viewed by first enabling Ludicrous Mode, so the staging-copy rule applies here too. It describes an hourly schedule option covering images from the theme and a handful of pre-configured plugin folders, and a folder list setting that takes full file-system paths.
Copy that folder list and the Exclude Images entries. Check wp-config.php for EWWW_IMAGE_OPTIMIZER_AUTO: the Override Options article says it enables or disables that hourly schedule and can be helpful to disable on staging and development sites, so look for it on a staging copy first.
Then read the server's own cron table, because the listing says batch image processes can be run through WP-CLI from regular cron instead of wp-cron.
The per-image controls are in the Media Library's list mode: the vendor's List Mode article puts options to optimise or re-optimise, restore and convert images in an Image Optimizer column, and a bulk option in the Bulk Actions menu.
The WordPress Users screen shows each user's role in its Role column. For each role you can already sign in as, starting with Author, note whether the column and its links appear.
Follow none of them: the How to use article says that on an image optimised before, the link that repeats the compression and the conversion links force the plugin to ignore any previous results and attempt further compression. Note whether wp-config.php sets EWWW_IMAGE_OPTIMIZER_DISABLE_CONVERT_LINKS, which the Override Options article says hides the conversion links.
The EWWW Image Optimizer security questions a version match cannot settle
A version inside an affected range in the history shows that a known record covers that copy of the plugin.
It does not show whether anyone used the flaw, what was saved in posts and uploads while that version ran, which wp-config.php constants override the settings page, or whether images leave the server for the Compress API or the Easy IO CDN.
A WordPress security audit signs in as each role with test accounts. Two of its checks sit closest to this plugin: as a contributor it saves a draft containing script and checks whether it is stripped before an editor previews it, and as an author it uploads files whose content does not match their extension, including SVG and HTML, and records what the server stores and serves.
Frequently asked questions
Each record answers in its own affected range and patched versions field, and not every range begins at the first release: CVE-2026-91051 runs from version 8.6.0 up to and including 8.7.7 and lists 8.8.0 as patched. Compare the installed version with every affected range in the history, because falling outside one range says nothing about the others.
Set the installed version, from the Description column of the WordPress Plugins screen, beside the update guidance at the top of the history. Then check which plugin you are reading: the vendor's article on which version to use says the old Cloud edition will no longer receive updates, and that a site still using it can get updates by installing the regular version, removing the Cloud version and then activating the regular one.
The records in the history are those the source data files under the slug ewww-image-optimizer, and being filed there does not settle how a record applies to a site on a paid plan. The vendor's Basic Configuration article says that when you purchase a premium plan you add your API key to the settings and then activate the Easy IO CDN. The listing says premium plans include the SWIS Performance plugin.
CVE-2023-40600 has a title ending "Unauthenticated Sensitive Information Exposure via Debug Log"; its affected range is all versions up to and including 7.2.0 and its patched versions field lists 7.2.1. The title is all the source data gives about that log, and it does not say which setting writes it. Separately, the vendor's List Mode article says the Show Metadata button in the Media Library's list mode is only available when debugging mode is active, so that button is one sign the mode is on. No page cited here ties that mode to the record.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 14 of the 15 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- EWWW Image Optimizer <= 8.9.1 - Unauthenticated Stored Cross-Site Scripting (CVE-2026-124254)
- EWWW Image Optimizer 8.7.4 - 8.9.0 - Authenticated (Author+) Stored Cross-Site Scripting (CVE-2026-91049)
- EWWW Image Optimizer <= 8.7.7 - Reflected Cross-Site Scripting via REQUEST_URI Parameter Key (CVE-2026-92826)
- EWWW Image Optimizer <= 8.7.7 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2026-97067)
- EWWW Image Optimizer 8.6.0 - 8.7.7 - Authenticated (Author+) PHP Object Injection (CVE-2026-91051)
- EWWW Image Optimizer <= 8.7.0 - Authenticated (Administrator+) Cross-Site WebP File Deletion or Rename (CVE-2026-91072)
- EWWW Image Optimizer <= 8.7.6 - Authenticated (Author+) Stored Cross-Site Scripting (CVE-2026-91011)
- EWWW Image Optimizer <= 8.7.6 - Unauthenticated Stored Cross-Site Scripting (CVE-2026-84773)
- EWWW Image Optimizer <= 8.7.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'data-script' Lazy Load Attribute in Post Content (CVE-2026-15446)
- EWWW Image Optimizer <= 7.2.3 - Cross-Site Request Forgery (CVE-2024-31924)
- EWWW Image Optimizer <= 7.2.0 - Unauthenticated Sensitive Information Exposure via Debug Log (CVE-2023-40600)
- EWWW Image Optimizer <= 7.2.0 - Sensitive Information Exposure
- EWWW Image Optimizer <= 5.8.1 - Cross-Site Request Forgery Bypass (CVE-2020-36750)
- EWWW Image Optimizer <= 2.8.4 - Remote Code Execution (CVE-2016-20010)
- EWWW Image Optimizer <= 2.0.1 - Reflected Cross-Site Scripting (CVE-2014-6243)