dbcve.org
ProfilepressWordPress extension · Properfraction

CVE-2023-50882

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 4.13.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in properfraction ProfilePress wp-user-avatar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ProfilePress: from n/a through <= 4.13.2.

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 confidence

Missing Authorization vulnerability in ProfilePress plugin's wp-user-avatar functionality allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to access or modify avatar settings they should not have permission to access.

MitigationImplement proper capability checks and role-based access controls on all wp-user-avatar endpoints and functions to ensure only authorized users can access avatar-related features.

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
Affected:< 4.13.3

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ProfilePress plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate ProfilePress (or Properfraction Profilepress). Check the version number displayed. Alternatively, check the plugin file header in /wp-content/plugins/profilepress/ folder for the Version: field.
    Affected if The installed version is below 4.13.3 (e.g., 4.13.2, 4.12.0, etc.)
  2. Confirm wp-user-avatar feature is active
    Check if the wp-user-avatar functionality is enabled on the site. This may be visible in ProfilePress settings under Avatar/Profile settings, or accessible via the /wp-user-avatar/ endpoint if publicly accessible. Look for user profile pages that display avatar upload/modify options.
    Affected if The wp-user-avatar functionality is accessible and enabled on the site, allowing users to modify avatar settings.
  3. Test authorization on avatar endpoints
    Attempt to access avatar-related endpoints or functions as a low-privilege user (subscriber or unauthenticated). Check if the plugin properly validates user capabilities before allowing avatar modifications. Common paths: /wp-admin/admin-ajax.php?action=pp_avatar_upload or similar ProfilePress AJAX actions.
    Affected if Users without administrator privileges can access or modify avatar settings that should require higher-level capabilities.

The environment is affected if ProfilePress version is below 4.13.3 AND the wp-user-avatar functionality is enabled and accessible without proper capability checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.13.3 or later
Fixed in 4.13.3
Interim mitigation

Implement proper capability checks and role-based access controls on all wp-user-avatar endpoints and functions to ensure only authorized users can access avatar-related features.

Recommended fix High confidence

ProfilePress 4.13.3 or later

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Find ProfilePress in the plugin list and check if an update is available.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 4.13.3 or later.
  5. 5. After updating, verify the plugin version shows 4.13.3 or higher under Plugins > Installed Plugins.
  6. 6. Test critical user functions (registration, login, profile management) to ensure the plugin operates correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Profilepress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50882 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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