# CVE-2026-15230: YayPricing < 3.5.7 - Subscriber+ Pricing Configuration Modification and Coupon Code Disclosure

> Authenticated subscribers can modify store pricing and view private coupon codes due to missing capability checks in REST API routes.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-rhmm-6m6v-j5v4

## What is CVE-2026-15230?

CVE-2026-15230 is a high-severity missing authorization vulnerability in Unknown YayPricing, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The YayPricing  WordPress plugin before 3.5.7 does not perform capability checks on several of its REST API routes, relying only on a shared nonce, allowing any authenticated user such as a subscriber to overwrite the store's pricing configuration and to disclose private coupon codes.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-15230?


## How do I fix CVE-2026-15230?

No fix has been published for CVE-2026-15230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15230 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15230 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15230 and fix it if it is affected.

What it is: CVE-2026-15230 is a high-severity missing authorization vulnerability in Unknown YayPricing, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15230 exists.

Affected product: Unknown YayPricing. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15230/ (Markdown: https://insights.sbomify.com/CVE-2026-15230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15230
- OSV: https://osv.dev/vulnerability/CVE-2026-15230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15230/
Summaries are generated and may contain mistakes; the official description above is the record.