Advanced Custom Fields (ACF®): A security weakness
Advanced Custom Fields (ACF®) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 6.8.1.
- Component
- Advanced Custom Fields (ACF®)
- Plugin slug
advanced-custom-fields- Affected
- <= 6.8.1
- Safe version
- See mitigation notes
- Published
- May 31, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published May 31, 2026 and is one of 20 known issues for this plugin.
Update, patch or deactivate.
No fixed release is identified. Update Advanced Custom Fields (ACF®) when a release after 6.8.1 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 6.8.9, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N