CVE-2026-97190 · Package
NO FIX YET · SEE WHAT TO DO
The Advanced Custom Fields plugin for WordPress skips an authorization check during bidirectional relationship sync. A contributor-level user can add or remove references to their own content on posts, users, or terms they are not allowed to edit.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Advanced Custom Fields WordPress plugin before 6.8.11 that use bidirectional relationship fields and have contributor-level or higher users. Sites on the fixed version or without bidirectional relationship fields are likely not affected. Sources do not give more detail on exact conditions.
Not affected if no-bidirectional-relationships, no-contributor-users, plugin-version-6.8.11-or-later
Who cares advanced-custom-fields, self-hosted, wordpress
6.8.11.6.8.11 or later, per the description (fixed before this version).The Advanced Custom Fields (ACF®) WordPress plugin before 6.8.11 does not verify that a user is allowed to edit the target object before writing to it during bidirectional relationship synchronization, allowing users with contributor-level access and above to add or remove a reference to their own object on arbitrary posts, users, or terms they cannot otherwise edit.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.