# CVE-2026-120534: Advanced Custom Fields: Extended PRO <= 0.9.2.6 - Unauthenticated Remote Code Execution via Dynamic Render Field Type


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-v5v5-hmcv-q4fc

## What is CVE-2026-120534?

CVE-2026-120534 is a critical vulnerability in ACF Extended Advanced Custom Fields: Extended PRO, published on 3 Nov 2026. 

### Official description

The Advanced Custom Fields: Extended PRO plugin for WordPress is vulnerable to Limited Code Injection in all versions up to, and including, 0.9.2.6 via the render_field function. This is due to insufficient validation of form configuration parameters before merging into field settings and passing to call_user_func_array in the render_field method. This makes it possible for unauthenticated attackers to call arbitrary WordPress functions with controlled arguments. Method 1 requires the administrator to enable the non-default 'shortcode_preview' setting for the target form, while Method 2 requires the server environment to lack OpenSSL functions, causing ACF Pro's acf_decrypt to fall back to unverified base64 decoding.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-120534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120534 is a critical vulnerability in ACF Extended Advanced Custom Fields: Extended PRO, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120534 in the wild and no public exploit code.

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

## Sources

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

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