# CVE-2026-14293: Autopay / Blue Media for WooCommerce < 5.0.1 - Unauthenticated Stored XSS via CSS Editor

> Unauthenticated attackers can inject malicious JavaScript into the checkout page via the CSS editor, potentially compromising administrator accounts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-pmwm-pj73-5hr6

## What is CVE-2026-14293?

CVE-2026-14293 is a high-severity cross-site scripting vulnerability in Unknown Autopay, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Autopay WordPress plugin before 5.0.1 does not perform any capability or nonce check before saving a styling option from a public request, and does not escape that value when it is later output on the checkout page, allowing unauthenticated attackers to store JavaScript that executes in the browser of any user, including administrators, who loads the checkout page.

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

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


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

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

## Is CVE-2026-14293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14293 is a high-severity cross-site scripting vulnerability in Unknown Autopay, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-14293 in the wild and no public exploit code.

Affected product: Unknown Autopay. 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-14293/ (Markdown: https://insights.sbomify.com/CVE-2026-14293/index.md)
```

## Sources

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

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