# CVE-2026-94264: Advanced Custom Fields: Extended 0.8.9.4 - 0.9.2.7 - Contributor+ XSS via Form Shortcode Attributes


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/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-x437-3m7g-hfr2

## What is CVE-2026-94264?

CVE-2026-94264 is a medium-severity 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 validate or escape some of its form shortcode attributes, which can be pointed at values taken from the visitor's own request and are then output without escaping, allowing users with a role as low as contributor to have arbitrary script run in the browser of anyone led to open a crafted link or page, including a logged-in administrator.
This is an incomplete fix for CVE-2023-5292, whose deny-list covers only the three HTML wrapper attributes.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-94264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94264 is a medium-severity vulnerability in Unknown Advanced Custom Fields: Extended, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94264 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-94264/ (Markdown: https://insights.sbomify.com/CVE-2026-94264/index.md)
```

## Sources

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

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