CVE
Envira Gallery privilege escalation in gallery permissions
- Exploited
- No known exploitation
- Fix
- Fixed in 1.16.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.16.4.
Summary
The Envira Gallery WordPress plugin, before the fixed release, does not apply its gallery-permission policy until an administrator opens its permissions screen after activation. As a result, a Contributor-level account can create, edit and delete galleries that should be limited to higher roles.
Original description
The Envira Gallery WordPress plugin before 1.16.4 does not apply its own gallery-permission policy until an administrator first opens its permissions screen, instead copying gallery-management capabilities onto each role from that role's core post capabilities after activation, which lets Contributor accounts create, edit and delete galleries that the policy is meant to restrict to higher roles.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.7/10CVSS 2.7
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 25 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.16.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-104683 (Envira Gallery < 1.16.4 - Contributor Incorrect Privilege Assignment via Gallery Capability Bootstrap), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-104683 (entry last updated 2026-11-18):
Affected:
- Unknown Envira Gallery: fixed in 1.16.4
Fixed versions: 1.16.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104683 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104683 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-104683
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-104683
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-104683"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Envira Gallery
fixed in 1.16.4
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-104683 |
| Record | NVD · CVE-2026-104683 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/af694353-1413-4b86-a2c0-513e640ca20d |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104683
Is CVE-2026-104683 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-104683?
Envira Gallery: before 1.16.4.Source: cve.now feed data
How do I fix CVE-2026-104683?
Upgrade to a fixed version: 1.16.4.Source: cve.now feed data