# CVE-2026-110039: Smush < 4.3.4 - Admin+ Network-Wide Plugin Settings Update on Multisite

> A site administrator can modify network-wide plugin settings in a WordPress multisite environment without proper authorization.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-w7j2-h466-h8g2

## What is CVE-2026-110039?

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

### Official description

The Smush  WordPress plugin before 4.3.4 does not restrict changes to a network-wide access setting to network administrators, allowing an administrator of a single site on a multisite network to change it for the entire network.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-110039 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110039 is a low-severity missing authorization vulnerability in Unknown Smush, published on 16 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-110039 in the wild and no public exploit code.

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

## Sources

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

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