HomeWordPress vulnerabilitiesSmush
Smush vulnerabilities
Smush has 5 known vulnerabilities in this database. The most recent published record is dated 27 Aug 2026.
- Known vulnerabilities
- 5
- Active installs
- 1m+
- Latest version
- 4.3.4
- Last updated
- 29 Sep 2026
- Most recent
- 27 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-19223 | High 7.2 | Before 4.3.2 | Fixed in 4.3.2 | 27 Aug 2026 |
| Path traversal CVE-2025-22288 | Medium 4.1 | Up to 3.17.0 | Fixed in a later version (latest 4.3.4) | 6 Nov 2025 |
| Broken access control CVE-2023-3352 | Medium 4.3 | Not yet published | Check for an update | 21 Jun 2024 |
| Cross-site scripting (XSS) CVE-2022-1009 | Medium 6.1 | Before 3.9.9 | Fixed in 3.9.9 | 30 May 2022 |
| Path traversal CVE-2017-15079 | High 7.5 | Up to 2.7.5 | Fixed in a later version (latest 4.3.4) | 6 Oct 2017 |
Read the published descriptions
- CVE-2026-19223, 27 Aug 2026
- The Smush WordPress plugin before 4.3.2 does not restrict a network-wide setting to network administrators, allowing an administrator of any single site on a multisite network to execute arbitrary code across the entire network. CVE record
- CVE-2025-22288, 6 Nov 2025
- Path Traversal: '.../...//' vulnerability in WPMU DEV - Your All-in-One WordPress Platform Smush Image Compression and Optimization wp-smushit allows Path Traversal.This issue affects Smush Image Compression and Optimization: from n/a through <= 3.17.0. CVE record
- CVE-2023-3352, 21 Jun 2024
- The Smush plugin for WordPress is vulnerable to unauthorized deletion of the resmush list due to a missing capability check on the delete_resmush_list() function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to delete the resmush list for Nextgen or the Media Library. CVE record
- CVE-2022-1009, 30 May 2022
- The Smush WordPress plugin before 3.9.9 does not sanitise and escape a configuration parameter before outputting it back in an admin page when uploading a malicious preset configuration, leading to a Reflected Cross-Site Scripting. For the attack to be successful, an attacker would need an admin to upload a malicious configuration file CVE record
- CVE-2017-15079, 6 Oct 2017
- The Smush Image Compression and Optimization plugin before 2.7.6 for WordPress allows directory traversal. CVE record
What to do if you run Smush
If you run Smush, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Smush vulnerabilities
Free. We email you when a new vulnerability is published for Smush, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.