# CVE-2026-94267: Advanced Custom Fields: Extended < 0.9.2.8 - Unauthenticated RCE via Front-End Post Update Action


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-69cf-82p8-9425

## What is CVE-2026-94267?

CVE-2026-94267 is a critical vulnerability in Unknown Advanced Custom Fields: Extended, published on 23 Oct 2026. 

### Official description

The Advanced Custom Fields: Extended WordPress plugin before 0.9.2.8, Advanced Custom Fields: Extended PRO WordPress plugin before 0.9.2.8 does not perform any capability check when updating a post through one of its front-end form actions, allowing unauthenticated visitors to overwrite arbitrary posts, including the ones in which the site stores its own field definitions, which in turn leads to arbitrary code execution on the server. Exploitation requires the site to publish a form whose post-update action maps both its target and its content to visitor-submitted values.

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

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


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

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

## Is CVE-2026-94267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94267 is a critical vulnerability in Unknown Advanced Custom Fields: Extended, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94267 in the wild and no public exploit code.

Affected product: Unknown Advanced Custom Fields: Extended. 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-94267/ (Markdown: https://insights.sbomify.com/CVE-2026-94267/index.md)
```

## Sources

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

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