Skip to main content
WordPress plugin recordReviewed

Smush vulnerability history, with a hands-off check of its image settings

Record titles in Smush's history end in wording that includes "Unauthenticated Denial of Service" and "Authenticated (Administrator+) Remote Code Execution".

Its changelog moves every setting to real-time auto-save at version 4.0, so each check here is read, write down, leave.

Smush vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 11 records for Smush. 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 4.3.6

Worked out from data retrieved on .

Every affected range listed in this source for Smush ends before version 4.3.6.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Smush - Image Optimization, Compression, Lazy Load, WebP & CDN < 4.3.6 - Authenticated (Author+) Insecure Direct Object Reference

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 4.3.6

    Patched versions: 4.3.6

    Update to at least version 4.3.6.

  2. Smush - Image Optimization, Compression, Lazy Load, WebP & CDN <= 4.3.5 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 4.3.5

    Patched versions: 4.3.6

    Update to at least version 4.3.6.

  3. Smush <= 4.3.3 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Low (CVSS 2.7)
    Affected versions
    • All versions up to and including 4.3.3

    Patched versions: 4.3.4

    Update to at least version 4.3.4.

  4. Smush - Image Optimization, Compression, Lazy Load, WebP & CDN < 4.3.2 - Authenticated (Administrator+) Remote Code Execution

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 4.3.2

    Patched versions: 4.3.2

    Update to at least version 4.3.2.

  5. Smush - Image Optimization, Compression, Lazy Load, WebP & CDN <= 4.2.0 - Unauthenticated Denial of Service

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 4.2.0

    Patched versions: 4.3.0

    Update to at least version 4.3.0.

Show 6 older records
  1. Smush Image Compression and Optimization <= 3.17.0 - Authenticated (Admin+) Directory Traversal

    Published:
    Last updated:
    Severity:
    Low (CVSS 2.7)
    Affected versions
    • All versions up to and including 3.17.0

    Patched versions: 3.17.1

    Update to at least version 3.17.1.

  2. Smush - Lazy Load Images, Optimize & Compress Images <= 3.16.4 - Missing Authorization to Resmush List Deletion

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 3.16.4

    Patched versions: 3.16.5

    Update to at least version 3.16.5.

  3. Smush - Lazy Load Images, Optimize & Compress Images <= 3.9.8 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)
    Affected versions
    • All versions up to and including 3.9.8

    Patched versions: 3.9.9

    Update to at least version 3.9.9.

  4. Smush - Lazy Load Images, Optimize & Compress Images <= 3.0.0 - Authenticated PHAR Deserialization

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 3.0.0

    Patched versions: 3.0.1

    Update to at least version 3.0.1.

  5. Smush - Lazy Load Images, Optimize & Compress Images <= 2.9.1 - Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 2.9.1

    Patched versions: 3.0.0

    Update to at least version 3.0.0.

  6. Smush - Lazy Load Images, Optimize & Compress Images <= 2.7.5 - Directory Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 2.7.5

    Patched versions: 2.7.6

    Update to at least version 2.7.6.

Check Smush 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 Smush touches: uploads, folders, settings and config files

Smush is an image optimiser from WPMU DEV.

Its WordPress.org listing says it compresses images as they are uploaded and in bulk, lazy loads them, and reaches images outside the media library through Directory Smush. The features the listing marks PRO include WebP and AVIF conversion and the image CDN. Read a Smush vulnerability record against that pipeline.

The vendor's guide says that with Automatic Compression enabled, images are optimised when they are uploaded to the Media Library regardless of the method, the WordPress or WooCommerce REST API and WordPress mobile apps included, and WordPress documents the Author role as holding upload_files. Settings sit on Smush's own screens.

WordPress documents an Administrator as having access to all administration features within a single site, and on multisite the guide's Permissions screen controls which Smush settings subsite administrators can override. The guide also describes a Configs screen that takes a configuration uploaded as a .json file.

Smush vulnerabilities as their titles word them

Titles in the history on this page name Cross-Site Scripting, Directory Traversal, Missing Authorization, Remote Code Execution, Denial of Service and PHAR Deserialization, some of them more than once.

Compare an installed version with each record's affected range and patched versions field:

  • CVE-2026-19223, whose title ends "Authenticated (Administrator+) Remote Code Execution". Affected: all versions before 4.3.2. Patched: 4.3.2.
  • CVE-2026-81285, whose title ends "Unauthenticated Denial of Service". Affected: all versions up to and including 4.2.0. Patched: 4.3.0. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
  • CVE-2023-3352, whose title ends "Missing Authorization to Resmush List Deletion". Affected: all versions up to and including 3.16.4. Patched: 3.16.5.

Same words, different records

Titles name the plugin several ways, so search the history by CVE id or version. More than one title ends "Cross-Site Scripting". CVE-2022-1009 covers all versions up to and including 3.9.8, with 3.9.9 patched. A record with no CVE id covers all versions up to and including 2.9.1, with 3.0.0 patched.

Here too the fields say nothing about the versions between the two, so for that record the patched version is the one to reach.

Where each Smush setting lives, and what to write down

Keep off the toggles.

The changelog on the WordPress.org listing introduces a reimagined interface with real-time auto-save for all settings at version 4.0, and the guide adds that a change to any setting that could affect optimisation savings triggers a scan automatically.

The guide describes that auto-saving interface, so an install from before that changelog entry may not match what follows. The guide introduces itself as covering Smush Pro's features, and this page says where it marks a chapter Pro.

If the Quick Setup Wizard opens, which the guide says happens the first time the plugin is activated or if its Reset option is used, press nothing in it and leave by the Skip start up wizard link or the X icon. The guide puts a Scan site button on its welcome screen, and says a later step applies settings that include Automatic Compression and Lazy Load & Preload.

Plugin version and edition

The Plugins screen gives the installed version in each row's Description column. 1 min read

Bulk optimisation

The guide's Dashboard chapter puts bulk work in a Media library panel whose controls include a Scan site button with the date and time of the last scan beside it, a compression level of Basic, Super or Ultra, a Backup original images option, and the button that starts optimising every uncompressed image in the Media Library. 1 min read

Lazy loading

The guide puts Lazy Load on the Lazy Load & Preload screen in the Smush menu, with its toggle at the top. 1 min read

CDN settings

The guide marks its CDN chapter Pro and says the CDN is enabled by selecting CDN from the menu. 1 min read

Image conversion options

Next-Gen Formats, which the guide marks Pro and lists under Settings, stores WebP or AVIF versions of Media Library images in a /smush-webp/ or /smush-avif/ folder in wp-content; when the CDN is active, the guide says the file format is configured there instead. 1 min read

Permissions, Configs and constants: Smush security a version does not record

A version match answers one question about a copy of Smush: which records have an affected range that includes it.

Whether a flaw was ever used is a separate question, and so is how the install is set up: the multisite Permissions choice, which saved Configs are listed ready to apply, and what changes Smush from outside its screens. The guide documents constants set in wp-config.php, such as WP_SMUSH_PARALLEL, and filters placed in a child theme's functions.php or a mu-plugin.

A WordPress security audit captures the requests an administrator makes in plugin settings screens and replays them as a subscriber. It does not include load or denial-of-service testing, so for CVE-2026-81285, whose title ends "Unauthenticated Denial of Service", the installed version against the record's fields is what there is to check.

Frequently asked questions

Each record has its own affected range and patched versions field. CVE-2025-22288, whose title ends "Authenticated (Admin+) Directory Traversal", covers all versions up to and including 3.17.0, with 3.17.1 patched. Compare the installed version with every affected range in the history on this page, then read the update guidance at the top of the history beside the plugin's changelog.

Compare the version on the Plugins screen with the update guidance at the top of the history. For a plugin hosted in its Plugin Directory, WordPress displays an update notice on that screen when a newer version is available. The vendor's WPMU DEV Dashboard guide describes a plugin manager whose top section shows which WPMU DEV plugins have updates available on a site that has that plugin installed. Before relying on the update guidance, read the changelog on the WordPress.org listing too: it marks security work with lines such as "Improvement: Security hardening", and a changelog line may have no matching record in the history on this page.

The records on this page are the ones the source data files under the WordPress.org slug wp-smushit. Being filed there does not settle whether a record applies to Smush Pro. The vendor's pages say how the editions arrive: the guide says WPMU DEV members can install Smush Pro directly to any connected site, and that sites hosted with WPMU DEV come with the Pro version installed automatically. The Smush Pro page keeps a changelog of its own, so write down which edition a site runs and read the matching changelog.

Off the site and back. The guide says the Smush API sends images via HTTPS to third-party servers, where they are compressed by writing temporary files to disk, and that the optimised images are returned to your server and the temporary files deleted immediately. Delivery is separate: with the Pro CDN enabled, the guide says an image that cannot be fetched from the CDN address is redirected to load from its original media library URL.

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 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 9 of the 11 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.