Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress Smush plugin allowed any logged-in user, even a subscriber, to delete the plugin’s resmush list. This is not a site takeover issue, but it can disrupt image optimization workflows and damage operational integrity where Smush is used.
Executive priority
Treat as a routine but real WordPress maintenance item. Prioritize sites with public registration, many subscribers, agencies, or shared editorial access, because the issue depends on authenticated low-privilege users.
Technical view
CVE-2023-3352 is a missing authorization issue in Smush’s delete_resmush_list() function. Authenticated attackers with low privileges could delete the resmush list for NextGEN or the Media Library. The CVSS 3.1 score is 4.3 with low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites running Smush versions in the reported affected range, up to and including 3.16.4, with untrusted or numerous authenticated users.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. Exploitation requires authenticated access, but only minimal privileges such as subscriber are reported as sufficient.
Researcher notes
This is CWE-862 missing authorization, not authentication bypass. The reported impact is unauthorized deletion of resmush list data, with no confidentiality or availability impact in the supplied CVSS vector. Evidence does not support broader product impact or weaponized exploitation claims.
Mitigation direction
- Inventory WordPress sites using the Smush plugin.
- Update Smush beyond the affected <= 3.16.4 range when vendor guidance confirms the fix.
- Limit unnecessary subscriber or low-privilege accounts on affected WordPress sites.
- Review vendor and WordPress plugin guidance for any additional remediation notes.
Validation and detection
- Confirm installed Smush versions across WordPress environments.
- Verify affected sites no longer run Smush <= 3.16.4.
- Check whether low-privilege users can change Smush resmush list state.
- Review audit logs for unexpected Smush or media optimization changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-3352 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
