CVE-2026-97193 · Package
NO FIX YET · SEE WHAT TO DO
The Secure Custom Fields WordPress plugin before 6.9.8 skips an authorization check when syncing bidirectional relationships. A logged-in contributor can add or remove references to their own objects on posts, users, or terms they cannot otherwise edit.
first public Nov 8, 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 Secure Custom Fields before 6.9.8 that use bidirectional relationship fields and have users with contributor access or above. Sites without multiple logged-in contributors or without relationship fields are less exposed.
Not affected if no-contributor-accounts, version-6.9.8-or-later
Who cares secure-custom-fields, self-hosted, wordpress
wp plugin get secure-custom-fields --field=version6.9.8 or laterThe Secure Custom Fields WordPress plugin before 6.9.8 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.