Extra User DetailsWordPress extension · Vadimk
CVE-2023-35877
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Vadym K. Extra User Details allows Stored XSS.This issue affects Extra User Details: from n/a through 0.5.
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 confidenceCSRF vulnerability in Vadym K. Extra User Details plugin (versions up to 0.5) allows attackers to forge requests that inject malicious JavaScript into user profile fields. Since the XSS is stored, it executes whenever other users view the affected user's profile details.
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
Extra User DetailsWordPress extension
< 0.5.1CVSS 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.
-
Check the installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > look for 'Vadimk Extra User Details' or 'Extra User Details' plugin. The version number is displayed below the plugin name.Affected if The version listed is below 0.5.1 (e.g., 0.5, 0.4, etc.)
-
Verify the plugin is activeIn the same plugins list, confirm the plugin has an 'Active' status indicator.Affected if The plugin is active and the version is below 0.5.1
-
Confirm user profile fields existGo to Users > Your Profile (or any user profile page) and scroll down to see if there are extra custom fields provided by this plugin (such as company, address, phone, or similar custom fields).Affected if The custom user profile fields are visible and the plugin version is vulnerable
-
Inspect profile field database entriesCheck the WordPress usermeta database table for any entries with meta_key related to the plugin (commonly prefixed with 'extra_' or similar). Use phpMyAdmin or WP-CLI: wp user meta list --user_id=1Affected if Profile meta fields exist and the plugin version is below 0.5.1
Your environment is affected if the Vadimk Extra User Details plugin is active at version 0.5 or below and custom user profile fields are present.
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.
From vendor data0.5.1
Implement anti-CSRF tokens (nonces) on all form submissions that modify user details and ensure proper sanitization/escaping when displaying user data. Users should upgrade to a patched version once available.
Fix this in Extra User Details
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35877 — 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-2023-35877 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