Skip to content
Web

CVE-2026-15230

8.1
High
EPSS 0.25%Patch availableAug 6, 2026

Authenticated users can overwrite pricing and expose private coupons via REST API.

common questions

Is CVE-2026-15230 being exploited?

Not confirmed. CVE-2026-15230 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-15230?

CVE-2026-15230 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15230?

Yes. A fix has been recorded for CVE-2026-15230. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15230 affect?

CVE-2026-15230 affects YayPricing WordPress plugin < 3.5.7, WordPress sites using YayPricing, WooCommerce stores using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15230?

Update YayPricing to ≥3.5.7, audit pricing/coupons, limit plugin access

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
YayPricing WordPress plugin < 3.5.7WordPress sites using YayPricingWooCommerce stores using the plugin
impact

Authenticated low-privilege users (e.g., subscriber) can modify store pricing configs and disclose private coupon codes via unprotected REST routes.

action required

Immediate action required

affected versions
Unknown YayPricing
  • affected< 3.5.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free