Quick answers
- Is CVE-2026-120534 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120534 being exploited in the wild.
- How severe is CVE-2026-120534?
- Critical severity, with a CVSS score of 9.8, published 3 November 2026.
- Which products and versions are affected?
- Advanced Custom Fields: Extended PRO up to and including 0.9.2.6.
- Is there a fix for CVE-2026-120534?
- Yes: fixed in 0.9.2.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120534 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120534?
- Check whether you run Advanced Custom Fields: Extended PRO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.9.2.8
Technical details
The render_field function in Advanced Custom Fields: Extended PRO insufficiently validates form configuration parameters before passing them to call_user_func_array, allowing unauthenticated code injection. Two attack methods exist: one requires the admin to enable a non-default shortcode_preview setting, while the second exploits environments lacking OpenSSL functions where ACF Pro's acf_decrypt falls back to unverified base64 decoding. This enables arbitrary WordPress function execution with attacker-controlled arguments on vulnerable sites.
Affected products
- Advanced Custom Fields Advanced Custom Fields: Extended PRO up to and including 0.9.2.6
Timeline
- 2026-11-03: disclosed