Wpengine Advanced Custom Fields (Acf®) vulnerabilities
3 vulnerabilities
Known vulnerabilities in Wpengine Advanced Custom Fields (Acf®), newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2026-4812wordpressadvanced-custom-fields+1
EPSS score0.86%
The Advanced Custom Fields (ACF) plugin for WordPress is vulnerable to Missing Authorization to Arbitrary Post/Page Disclosure in versions up to and including 6.7.0. This is due to AJAX field query endpoints accepting user-supplied filter parameters that override field-configured restrictions without proper authorization checks. This makes it possible for unauthenticated attackers with access to a frontend ACF form to enumerate and disclose information about draft/private posts, restricted post types, and other data that should be restricted by field configuration.CVE-2026-8382wordpressadvanced-custom-fields+1EPSS score0.52%
The Advanced Custom Fields (ACF®) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.8.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the post_title and post_content of any post bound to a publicly accessible acf_form() instance by injecting values into the _post_title and _post_content parameters of a form submission request.CVE-2023-6701advancedcustomfieldsadvanced_custom_fields+4EPSS score0.52%
The Advanced Custom Fields (ACF) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via a custom text field in all versions up to, and including, 6.2.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.