User Registration \& MembershipWordPress extension · Wpeverest
CVE-2025-39400
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpeverest User Registration user-registration allows Reflected XSS.This issue affects User Registration: from n/a through < 4.2.0.
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 · high confidenceA reflected Cross-site Scripting (XSS) vulnerability exists in the User Registration WordPress plugin by wpeverest. The vulnerability allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in the web page response. This affects versions prior to 4.2.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
User Registration \& MembershipWordPress extension
< 4.2.0< 5.2.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 User Registration plugin is installedNavigate to WordPress admin dashboard > Plugins. Look for 'User Registration' or 'User Registration & Membership' by wpeverest in the installed plugins list.Affected if Plugin is not installed or not found in the plugins list
-
Check installed plugin versionIn WordPress admin > Plugins page, click on the plugin name to view its details, or check the plugin header in /wp-content/plugins/user-registration/user-registration.php for the 'Version' field.Affected if Installed version is below 4.2.0 or below 5.2.0 (whichever version branch is in use)
-
Confirm user registration form is activeNavigate to User Registration > All Forms in the admin panel. Verify that at least one registration form exists and is published.Affected if A registration form exists and is publicly accessible
-
Check if registration pages are publicly accessibleVisit the registration page URL (commonly /registration or the slug set in plugin settings). Attempt to submit test input containing HTML/script tags to observe if input is reflected without encoding.Affected if User input is reflected back in the response without proper sanitization or encoding
Environment is affected if User Registration plugin version is below 4.2.0 (or 5.2.0) AND a registration form is publicly accessible, allowing reflected XSS injection.
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 · scoped4.2.05.2.0
Upgrade the User Registration plugin to version 4.2.0 or later to receive the patch that properly neutralizes user input during page generation.
User Registration & Membership version 4.2.0 (or 5.2.0 for the 5.x branch)
- Backup your WordPress site and database before making any changes
- Update the User Registration & Membership plugin to version 4.2.0 or higher (for 4.x branch)
- Alternatively, update to version 5.2.0 or higher (for 5.x branch)
- Verify the update was successful by checking the plugin version in WordPress admin under Plugins
- Test that the User Registration forms function correctly after the update
- Clear any site caches if applicable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in User Registration \& Membership
Scoped from the published advisory
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39400 — 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-2025-39400 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