# CVE-2026-14331: Subscribe2 < 10.46 - Reflected XSS via email Parameter

> An attacker can execute arbitrary JavaScript in the browser of an unauthenticated visitor via a crafted link in the Subscribe2 WordPress plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-m3cj-4969-qh2q

## What is CVE-2026-14331?

CVE-2026-14331 is a medium-severity cross-site scripting vulnerability in Unknown Subscribe2, published on 7 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 Subscribe2  WordPress plugin before 10.46 does not properly escape a user-supplied value before reflecting it into a public subscription form, leading to Reflected Cross-Site Scripting that executes in the browser of an unauthenticated visitor who interacts with the form through a crafted link.

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

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


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

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

## Is CVE-2026-14331 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14331 is a medium-severity cross-site scripting vulnerability in Unknown Subscribe2, published on 7 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14331 exists.

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

## Sources

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

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