The Smush WordPress plugin before 4.3.6 does not verify that a user is authorised to act on the targeted media
Source GCVE Database
Not known to be exploited : upgrade to 4.3.6 soon.
Data as of 11 Nov 2026, 07:47 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.3.6
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Smush (WordPress plugin) to 4.3.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Smush | Affected
| Fixed in
|
AI-suggested
Upgrade the Smush WordPress plugin to version 4.3.6 or later, where this authorization check issue is fixed. There is no indication of an official patch link in the provided data, but the fixed version is explicitly stated. Until upgraded, restrict Author role permissions if possible to limit exposure.
Description
The Smush WordPress plugin versions before 4.3.6 have an authorization flaw where users with the Author role or higher can optimize and restore media attachments owned by other users. This occurs because the plugin only checks a broad upload-files capability rather than verifying specific ownership or authorization for the targeted media. This allows unauthorized modification of other users' media files and consumption of stored backups.