The Envira Gallery WordPress plugin before 1.16.4 does not apply its own gallery-permission policy until an
Source GCVE Database
Not known to be exploited : upgrade to 1.16.4 soon.
Data as of 18 Nov 2026, 08:19 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 1.16.4
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 17 Nov 2026.
What to do
Upgrade Envira Gallery (WordPress plugin) to 1.16.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Envira Gallery | Affected
| Fixed in
|
AI-suggested
Upgrade to Envira Gallery version 1.16.4 or later where this issue is fixed. Until then, administrators should open the permissions screen after plugin activation to apply the correct gallery-permission policy. No other mitigations are specified.
Description
The Envira Gallery WordPress plugin versions prior to 1.16.4 have a permissions enforcement issue where the gallery-permission policy is not applied until an administrator opens the permissions screen. Until then, gallery-management capabilities are copied from core post capabilities to each role, allowing Contributor accounts to create, edit, and delete galleries despite intended restrictions.