# CVE-2026-104684: Envira Gallery < 1.16.2 - Author+ IDOR via Shortcode

> Authors can expose non-public gallery metadata to unauthenticated visitors via shortcode embedding due to missing authorization checks.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-42w6-r5c3-5hw2

## What is CVE-2026-104684?

CVE-2026-104684 is a low-severity missing authorization vulnerability in Unknown Envira Gallery, published on 11 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Envira Gallery  WordPress plugin before 1.16.2 does not verify that a user is authorized to read a gallery before rendering it, allowing authors to embed and expose other users' non-public gallery metadata to unauthenticated visitors.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-104684?


## How do I fix CVE-2026-104684?

No fix has been published for CVE-2026-104684 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104684 being exploited?

There is no known exploitation of CVE-2026-104684 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104684 and fix it if it is affected.

What it is: CVE-2026-104684 is a low-severity missing authorization vulnerability in Unknown Envira Gallery, published on 11 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104684 in the wild and no public exploit code.

Affected product: Unknown Envira Gallery. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104684/ (Markdown: https://insights.sbomify.com/CVE-2026-104684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104684
- OSV: https://osv.dev/vulnerability/CVE-2026-104684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104684/
Summaries are generated and may contain mistakes; the official description above is the record.