# CVE-2026-87888: YayPricing < 3.5.7 - Subscriber+ Stored XSS via save_page_data REST Route

> Subscribers can inject JavaScript via a REST route that executes in admin browsers, potentially leading to account takeover.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2026
- **Updated:** 12 Sep 2026
- **Also known as:** GHSA-7hp7-3c46-m2c9

## What is CVE-2026-87888?

CVE-2026-87888 is a high-severity cross-site scripting vulnerability in Unknown YayPricing, published on 12 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-87888 being exploited?

There is no known exploitation of CVE-2026-87888 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87888 is a high-severity cross-site scripting vulnerability in Unknown YayPricing, published on 12 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-87888 in the wild and no public exploit code.

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-87888/ (Markdown: https://insights.sbomify.com/CVE-2026-87888/index.md)
```

## Sources

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

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