CVE-2026-119521 WordPress Paid Member Subscriptions plugin <= 3.1.3 - Cross Site Scripting (XSS) vulnerability
Medium 6.5
Published
Updated
Check this codebase for CVE-2026-119521 and fix it if it is affected.
What it is: CVE-2026-119521 is a medium-severity vulnerability in Cozmoslabs Paid Member Subscriptions, published on 3 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-119521 in the wild and no public exploit code.
Affected product: Cozmoslabs Paid Member Subscriptions. 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-119521/ (Markdown: https://insights.sbomify.com/CVE-2026-119521/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119521?
CVE-2026-119521 is a medium-severity vulnerability in Cozmoslabs Paid Member Subscriptions, published on 3 Nov 2026.
Official description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cozmoslabs Paid Member Subscriptions paid-member-subscriptions allows Stored XSS.This issue affects Paid Member Subscriptions: from n/a through 3.1.3.
Weakness: CWE-79
Which versions are affected by CVE-2026-119521?
How do I fix CVE-2026-119521?
No fix has been published for CVE-2026-119521 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119521 being exploited?
There is no known exploitation of CVE-2026-119521 in the wild and no public exploit code.
Sources
Also known as GHSA-vrqc-4rp8-xrxq.