ProfilepressWordPress extension · Properfraction
CVE-2023-23820
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in ProfilePress Membership Team ProfilePress plugin <= 4.5.4 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 · high confidenceAuthenticated users with contributor-level permissions can inject malicious JavaScript code into team profile fields in the ProfilePress plugin. This stored XSS executes when other users or administrators view the affected profile pages.
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
ProfilepressWordPress extension
< 4.5.5CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 ProfilePress plugin is installedNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate the ProfilePress plugin entry. Note the version number displayed.Affected if ProfilePress is installed and the version shown is lower than 4.5.5 (e.g., 4.5.4, 4.5.3, etc.)
-
Confirm contributor role has profile accessGo to ProfilePress > Settings > Roles & Capabilities, or check WordPress Users > Roles to see if contributor role has been granted profile creation or editing capabilities.Affected if Contributor-level users can create or edit user profiles in the plugin settings.
-
Inspect team profile field configurationNavigate to ProfilePress > Profile Fields or Team Members section in the admin panel. Examine the profile field settings to see if fields accept user-supplied input without restrictions.Affected if Profile fields are configured to accept freeform text input from contributor-level users without input validation controls visible.
Your environment is affected if the ProfilePress plugin version is below 4.5.5 AND contributor-role users have access to create or edit profile fields that accept unvalidated user input.
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.5.5
Upgrade the ProfilePress plugin to a version newer than 4.5.4, which should contain proper input sanitization and output encoding for profile fields.
ProfilePress 4.5.5 or later
- 1. Backup your WordPress site before making any changes
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Locate ProfilePress in the plugin list
- 4. Click 'Update now' if an update is available, or download version 4.5.5 from the WordPress plugin repository and upload it manually
- 5. After updating, verify the plugin status shows version 4.5.5 or higher
- 6. Test the membership profile functionality to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Profilepress
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23820 — 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-23820 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