# CVE-2026-16057: Contest Gallery < 30.0.7 - Author+ Arbitrary Post Deletion via post_cg_youtube_delete_from_library

> Author-level users can delete arbitrary posts and pages due to missing per-object authorization checks in the Contest Gallery plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-pwq7-3xxm-qxqg

## What is CVE-2026-16057?

CVE-2026-16057 is a medium-severity missing authorization vulnerability in Unknown Contest Gallery, published on 3 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Contest Gallery  WordPress plugin before 30.0.7 does not perform per-object capability or nonce checks in one of its post-deletion handlers, gating it only by a coarse role-membership test, which allows any Author-level or higher user to permanently delete arbitrary posts, pages, and other content they do not own.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-16057 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: Unknown Contest 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-16057/ (Markdown: https://insights.sbomify.com/CVE-2026-16057/index.md)
```

## Sources

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

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