CVE-2026-97195 · Package
NO FIX YET · SEE WHAT TO DO
The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a saved field definition before printing part of it as an HTML attribute name. A user who can configure fields can store a script that runs in the browser of anyone who views a page showing that field, which on multisite lets a site administrator without unfiltered_html inject script into other users' sessions.
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 the Secure Custom Fields plugin before 6.9.8 where users can edit field definitions. The risk is highest on WordPress multisite, where a site administrator lacking unfiltered_html can inject script affecting other users. Sites without the plugin, or running 6.9.8 or later, are not affected.
Not affected if no-field-editing-users, plugin-version-6.9.8-or-later
Who cares multisite, secure-custom-fields, wordpress
wp plugin get secure-custom-fields --field=version6.9.8 or later (per the advisory's 'before 6.9.8')The Secure Custom Fields WordPress plugin before 6.9.8 does not sanitize a persisted field definition before emitting part of it as an HTML attribute name, allowing a user able to configure its fields to store a payload that executes as JavaScript in the browser of any user who views a page rendering the affected field, which on multisite lets a site administrator who lacks the unfiltered_html capability inject script into other users' sessions.
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.