CVE-2023-3352

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

2024-06-20 00:00
Truoc Phan

Strategic Overview

Status
Patched in 3.16.5
Affected Plugin
Smush – Image Optimization, Compression, Lazy Load, WebP & CDN
Affected Version
<= 3.16.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-3352
View all Smush – Image Optimization, Compression, Lazy Load, WebP & CDN vulnerabilities

At a glance

CVE-2023-3352 is a medium-severity Missing Authorization vulnerability in the Smush WordPress plugin, affecting versions <= 3.16.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.16.5; sites on affected versions should update now. Disclosed June 2024, reported by Truoc Phan.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Smush <= 3.16.4 carries this weakness at delete_resmush_list(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Smush the fix is 3.16.5: builds <= 3.16.4 are affected, anything from 3.16.5 onward is not.

Remediation

Update to version 3.16.5, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Smush 3.16.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-3352https://www.wordfence.com/threat-intel/vulnerabilities/id/dfbaa3e4-40c2-41d8-996c-232e27a04b73https://nvd.nist.gov/vuln/detail/CVE-2023-3352

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C