# CVE-2026-16623: Create Block Theme < 2.10.0 - Admin+ PHP Code Injection via Pattern Save (Multisite)

> A multisite administrator can inject and execute arbitrary PHP code via pattern saving in the Create Block Theme plugin.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/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:** 4 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-6wqp-7cwm-r4gv

## What is CVE-2026-16623?

CVE-2026-16623 is a high-severity code injection vulnerability in Unknown Create Block Theme, published on 4 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Create Block  WordPress plugin before 2.10.0 does not correctly escape user-supplied text before writing it into a generated PHP pattern file, allowing a multisite subsite administrator (who holds the capability gating this action but is denied the capability that normally gates PHP file editing) to inject and execute arbitrary PHP code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-16623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16623 is a high-severity code injection vulnerability in Unknown Create Block Theme, published on 4 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-16623 in the wild and no public exploit code.

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

## Sources

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

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