The Advanced Custom Fields: Extended PRO plugin for WordPress is vulnerable to Limited Code Injection in all versions
Source GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 3 Nov 2026, 07:42 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 that the server environment has OpenSSL functions available to prevent fallback to insecure base64 decoding. Monitoring vendor channels for updates is recommended.
Description
The Advanced Custom Fields: Extended PRO plugin for WordPress up to version 0.9.2.6 is vulnerable to a limited code injection vulnerability via the render_field function. This flaw arises from insufficient validation of form configuration parameters, allowing unauthenticated attackers to invoke arbitrary WordPress functions with controlled arguments. Exploitation requires either enabling the non-default 'shortcode_preview' setting or a server environment lacking OpenSSL functions, which causes fallback to unverified base64 decoding.