CVE-2026-94263: Advanced Custom Fields content injection vulnerability
medium 4.8 published 2026-10-23
- Affected versions
- 0.9.2.4 up to (not including) 0.9.2.8
- Fixed in
- 0.9.2.8
- Latest version
- 0.9.2.8
- Severity
- Medium · CVSS 4.8
- Active installs
- 100,000+
- Type
- Content injection
What an attacker needs
- Access: None. No account or login is needed.
CVSS vector (score by WPScan): CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
What to do now
- Update Advanced Custom Fields to 0.9.2.8 or newer: Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- Not sure which version you run? Check your version against every known Advanced Custom Fields issue.
With WP-CLI:
wp plugin get acf-extended --field=version. - If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.
The advisory
The Advanced Custom Fields: Extended and Advanced Custom Fields: Extended PRO WordPress plugins from 0.9.2.4 to 0.9.2.7 do not consistently disable shortcode processing in the confirmation message of their front-end forms, allowing unauthenticated visitors to have arbitrary shortcodes executed server-side when they submit a form whose stored configuration does not carry the relevant setting.
References
- NVD CVE-2026-94263 nvd.nist.gov
- WPScan advisory wpscan.com
Related
Ran an affected version? Check your site for signs of a hack
The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.
Where this data comes from
- CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Versions and install counts: wordpress.org/plugins/acf-extended (Plugins API), fetched 2026-11-04.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.