# CVE-2026-106095: Code Snippets < 3.10.0 - Admin+ Network-Scoped Snippet Activation and Deactivation via update_code_snippet

> A single-site administrator can activate or modify network-wide code snippets due to missing capability checks, potentially executing arbitrary code across the entire multisite network.

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

## What is CVE-2026-106095?

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

### Official description

The Code Snippets WordPress plugin before 3.10.0 does not perform a capability check on one of its snippet-management actions and derives the network scope of the targeted snippet from the request instead of from the stored record, allowing an administrator of a single subsite on a multisite network to activate, deactivate and reprioritise network-scoped snippets that run across every site in the network.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106095 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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