# CVE-2026-110029: Squeeze < 1.8.1 - Subscriber+ Missing Authorization via squeeze_restore_attachment

> Authenticated subscribers can revert or delete attachments and backups in the Squeeze WordPress plugin due to missing capability checks.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-486q-7jvh-4x7q

## What is CVE-2026-110029?

CVE-2026-110029 is a medium-severity missing authorization vulnerability in Unknown Squeeze, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Squeeze WordPress plugin before 1.8.1 does not perform a capability check on one of its AJAX actions, allowing authenticated users with a role as low as Subscriber to revert any attachment to its backup copy and to permanently delete that backup and the plugin's generated WebP derivatives, regardless of ownership.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110029 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110029 is a medium-severity missing authorization vulnerability in Unknown Squeeze, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110029 in the wild and no public exploit code.

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

## Sources

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

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