YayPricing lets subscribers store scripts in pricing rules
YayPricing before 3.5.7 exposes a REST route that saves pricing rules without checking authorization. A subscriber can store JavaScript in a rule; it executes in an administrator's browser when the administrator opens the plugin settings page. The authoritative export does not name the route, request field, or output context.
- Component
- YayPricing
- Plugin slug
yaypricing- Affected
- < 3.5.7
- Safe version
3.5.7- Published
- Sep 12, 2026
This CVE was published Sep 12, 2026 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update YayPricing to 3.5.7 or later. The authoritative affected range ends before 3.5.7. The application-level fix must require the plugin-management capability on the REST route, sanitize stored rule fields, and escape each value for its settings-page output context.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
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 YayPricing WordPress plugin before 3.5.7 does not perform an authorization check on a REST route that saves its pricing rules, allowing users with the subscriber role and above to store JavaScript that executes in the browser of an administrator who opens the YayPricing WordPress plugin before 3.5.7's settings page.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H