CVE-2026-120534: Advanced Custom Fields: Extended PRO (WordPress plugin) · Unrestricted File Upload
Affects Advanced Custom Fields: Extended PRO (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 3 Nov 2026, 05:13 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 9.8 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ACF ExtendedAdvanced Custom Fields: Extended PRO | Affected
| Fixed in– |
AI-suggested
Until a fix is available, administrators should avoid enabling the 'shortcode_preview' setting and ensure the server environment includes OpenSSL functions to prevent fallback to insecure decoding. Monitor vendor channels for updates and apply patches promptly once released.
Description
The Advanced Custom Fields: Extended PRO WordPress plugin up to version 0.9.2.6 contains a critical vulnerability allowing unauthenticated attackers to perform limited code injection via the render_field function. This occurs due to insufficient validation of form configuration parameters, enabling arbitrary WordPress function calls with attacker-controlled arguments. Exploitation requires either enabling a non-default shortcode_preview setting or the absence of OpenSSL functions on the server.