Secure Custom Fields stored XSS in field rendering
Secure Custom Fields
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Unknown Secure Custom Fields |
| No fix yet |
Original description
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.
From the CVE record · WPScan