Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify vulnerable ACF Extended PRO form endpoint
-
DeliverySubmit crafted form configuration parameters
-
ExploitParameters merged into field settings in render_field
-
Executioncall_user_func_array invokes arbitrary WordPress function with controlled args
-
ImpactFull site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation is unauthenticated (PR:N) but requires ONE of two non-default preconditions. Method 1: an administrator must have enabled the non-default 'shortcode_preview' setting on the specific target form. Method 2: the server environment must lack OpenSSL functions, causing ACF Pro's acf_decrypt to fall back to unverified base64 decoding of attacker-supplied data. Limiting factors: default installations (shortcode_preview disabled AND OpenSSL present) are not exploitable, which substantially narrows the realistically affected population below what the 9.8/AV:N rating suggests; only ACF Extended PRO versions up to and including 0.9.2.6 are affected. |
| Impact | The signals pull in two directions and must be reconciled. The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8) and the vuln.today 'act_now' Decision label both frame this as trivially exploitable unauthenticated critical RCE. However, the description itself reveals that exploitation is gated behind one of two non-default preconditions - Method 1 needs an administrator to have enabled the non-default 'shortcode_preview' setting on the target form, and Method 2 needs the server to lack OpenSSL functions so ACF Pro's acf_decrypt falls back to unverified base64 decoding. That contradicts the AC:L rating: because success depends on a target-side configuration the attacker does not control, real-world attack complexity is higher than 9.8 implies, and default, OpenSSL-equipped installations with shortcode_preview off are not exploitable. No EPSS score, no CISA KEV listing, and no exploit/PoC reference are present in the supplied data, so there is no evidence of active exploitation or public weaponization - the urgency rests on the Wordfence report and the act_now label, not on observed in-the-wild activity. Net: treat as a high-priority patch because the unauthenticated-to-full-compromise impact is severe where conditions are met, but recognize the exploitable population is a conditional subset rather than every install. Authentication requirement is confirmed unauthenticated by PR:N in the provided vector. |
| Exploit ScenarioDerived | A remote unauthenticated attacker locates a WordPress site running ACF Extended PRO (≤0.9.2.6) that either has the non-default 'shortcode_preview' setting enabled on a form (Method 1) or runs on a server without OpenSSL functions (Method 2), then submits crafted form configuration parameters. Those parameters are merged into field settings and passed to call_user_func_array in render_field, letting the attacker invoke arbitrary WordPress functions with attacker-controlled arguments and compromise the site. No public exploit identified at time of analysis; the network attack vector is offset by the required non-default precondition. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Unauthenticated attackers can invoke arbitrary WordPress functions with attacker-controlled arguments through the render_field method in the Advanced Custom Fields: Extended PRO plugin for WordPress, affecting all versions up to and including 0.9.2.6. Exploitation is not unconditional: it requires either the non-default 'shortcode_preview' setting to be enabled on the targeted form, or a server environment lacking OpenSSL functions so that ACF Pro's acf_decrypt falls back to unverified base64 decoding - default installations with shortcode_preview disabled and OpenSSL present are not exploitable. No public exploit code and no confirmed active exploitation were identified at time of analysis, but the vendor-reported severity is critical and the priority decision is act_now, so exposed sites running the PRO plugin should be triaged promptly.
RemediationAI
No vendor-released fix version is specified in the available data, so confirm the current release and the version that corrects render_field by checking the ACF Extended changelog at https://www.acf-extended.com/changelog and the Wordfence advisory before upgrading past 0.9.2.6. Because exploitation depends on one of two non-default conditions, the two directly effective compensating controls are: turn off (or confirm it is off) the shortcode_preview setting on every form, since enabling it opens the first exploitation path - the trade-off is that form designers lose shortcode preview rendering in the admin; and ensure the PHP OpenSSL extension is installed and enabled so ACF Pro's acf_decrypt does not fall back to unverified base64 decoding, which closes the second path but must be validated against the host's PHP build and may not be possible on constrained shared hosting. Neither control repairs the underlying missing validation in render_field, so they are interim measures pending a patched plugin release; remove or deactivate the PRO plugin on sites that cannot satisfy either condition.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in the render_field function of ACF Extended PRO, a WordPress plugin that extends Advanced Custom Fields. Form configuration parameters are merged into field settings without sufficient validation before being handed to call_user_func_array, the PHP dynamic-dispatch primitive that invokes a callback with a supplied argument array; because the callback name and arguments both derive from unvalidated configuration, an attacker who can influence that configuration reaches arbitrary WordPress function calls. The supplied CWE mapping is CWE-434 (Unrestricted Upload of File with Dangerous Type), while the described mechanism is closer to code injection through dynamic function invocation - the discrepancy is worth noting when reconciling scanner output against the advisory. Reachability is gated by two environment-dependent paths: the first requires an administrator to have turned on the non-default shortcode_preview option for the specific target form, and the second requires the PHP environment to lack OpenSSL functions, forcing ACF Pro's acf_decrypt to fall back to base64 decoding of attacker-supplied data without integrity verification. The independent assessment therefore scores AC:H rather than the vendor's AC:L, because the attack is unauthenticated (PR:N) but contingent on one of these non-default preconditions, which substantially narrows the realistically affected population compared with a 9.8 rating.
Know when Advanced Custom Fields gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated network-reachable (PR:N, AV:N), but success depends on a non-default target configuration the attacker cannot control, so AC:H; arbitrary WordPress function calls yield full C/I/A:H.
Primary rating from Vendor (Wordfence).
CVSS VectorNVD
DescriptionNVD
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.
Articles & Coverage 2
Executive ViewAI
CVE-2026-120534 is a critical vulnerability in the Advanced Custom Fields: Extended PRO plugin for WordPress, affecting all versions up to 0.9.2.6. While exploitation is conditional (requiring a non-default setting or missing OpenSSL), the potential impact on affected sites is severe, allowing unauthenticated attackers to execute arbitrary WordPress functions. Leadership should prioritize immediate triage of all sites running this PRO plugin to prevent potential compromise.
No vendor-released patch identified at time of analysis; interim mitigations include disabling the 'shortcode_preview' setting and ensuring OpenSSL functions are enabled on the server.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
More in Advanced Custom Fields
View allThe Advanced Custom Fields (ACF) Free and Pro WordPress plugins 6.x before 6.1.0 and 5.x before 5.12.5 unserialize user
The Advanced Custom Fields WordPress plugin before 5.12.3, Advanced Custom Fields Pro WordPress plugin before 5.12.3 all
Unauthenticated administrator account takeover in the Advanced Custom Fields: Extended WordPress plugin before 0.9.2.7 i
Privilege escalation to administrator in the Advanced Custom Fields: Extended WordPress plugin before 0.9.2.7 allows una
The Secure Custom Fields WordPress plugin before 6.3.9, Secure Custom Fields WordPress plugin before 6.3.6.3, Advanced C
The Advanced Custom Fields (ACF) WordPress plugin before 6.3, Advanced Custom Fields Pro WordPress plugin before 6.3 all
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
The Advanced Custom Fields Pro WordPress plugin before 5.9.1 did not properly escape the generated update URL when outpu
Unauthenticated privilege escalation in the Advanced Custom Fields: Extended (ACFE) WordPress plugin through version 0.9
Arbitrary file deletion in the Novarain/Tassos Framework system plugin (plg_system_nrframework) and the suite of Tassos.
Improper shortcode handling in the Advanced Custom Fields: Extended and ACF Extended PRO WordPress plugins (versions 0.9
Sensitive information exposure in the Advanced Custom Fields: Extended WordPress plugin (all versions up to and includin
EUVD-2026-115668
GHSA-v5v5-hmcv-q4fc
NVD
CVE.org
EPSS
Exploit-DB