CVE-2026-39514
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Cross Site Scripting (XSS) in Paid Member Subscriptions <= 2.17.3 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnauthenticated Cross Site Scripting (XSS) vulnerability in the Paid Member Subscriptions WordPress plugin versions 2.17.3 and below allows remote attackers to inject malicious JavaScript code through unprotected user input fields.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Paid Member Subscriptions plugin is installedNavigate to WordPress Admin > Plugins and locate 'Paid Member Subscriptions' in the list of installed pluginsAffected if Plugin is not present in the plugins list
-
Determine installed plugin versionIn the Plugins list, locate the version number displayed under the plugin name, or check the plugin header in /wp-content/plugins/paid-member-subscriptions/readme.txt or the main plugin file for the Version constantAffected if Version is 2.17.3 or lower
-
Confirm plugin is activeIn WordPress Admin > Plugins, verify the plugin status shows 'Active' rather than 'Inactive'Affected if Plugin is active with a vulnerable version
-
Identify exposed user input fieldsVisit public-facing pages that contain Paid Member Subscriptions forms (registration, login, subscription, profile edit) and inspect HTML input fields for lack of output sanitization - specifically test that user-supplied data in form fields is reflected in the page without encodingAffected if User input fields in plugin forms are present and accessible to unauthenticated users
If Paid Member Subscriptions plugin version 2.17.3 or below is installed and active, the environment is affected by this unauthenticated XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Paid Member Subscriptions plugin to the latest version beyond 2.17.3, or apply vendor-provided security patches to address the XSS vulnerability.
Paid Member Subscriptions version 2.17.4 or later (any stable release above 2.17.3)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Paid Member Subscriptions' plugin
- Check the current version number to confirm it is 2.17.3 or lower
- Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
- After updating, verify the plugin is running version 2.17.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39514 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data