dbcve.org
ProfilepressWordPress extension · Properfraction

CVE-2023-44150

HIGH · 7.5 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 4.13.3 or later.
See remediation →
84/100
Remediation priority · High
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ProfilePress Membership Team Paid Membership Plugin, Ecommerce, Registration Form, Login Form, User Profile & Restrict Content – ProfilePress.This issue affects Paid Membership Plugin, Ecommerce, Registration Form, Login Form, User Profile & Restrict Content – 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

An information disclosure vulnerability in ProfilePress WordPress plugin allows unauthorized actors to access sensitive information. The vulnerability affects versions up to and including 4.13.2, with a CVSS score of 7.5 indicating high severity but with network-exploitable attack vector.

MitigationUpdate ProfilePress plugin to the latest version once a patch is released, or apply vendor-supplied security updates. Review access logs and user accounts for any unauthorized access indicators.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check installed ProfilePress version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > locate ProfilePress and read the version number displayed under the plugin name
    Affected if The version displayed is 4.13.2 or lower, or shows any version prior to 4.13.3
  2. Verify WordPress is accessible over network
    Confirm the WordPress site is publicly accessible or accessible from untrusted network segments by checking the site URL accessibility
    Affected if The WordPress site is reachable over the network (including internal networks) and ProfilePress version is 4.13.2 or lower
  3. Identify if ProfilePress user registration is enabled
    Check WordPress admin > ProfilePress > Settings > ensure the plugin is actively handling user registration, login, or profile management functions
    Affected if The plugin is actively processing user forms or authentication functions and the version is vulnerable
  4. Review access logs for suspicious requests
    Examine web server access logs (Apache/Nginx) for unusual GET or POST requests to ProfilePress endpoints, particularly those targeting user data or configuration files
    Affected if Unusual or unauthorized API requests to ProfilePress-related paths are found in logs from external IPs

A user is affected if their ProfilePress plugin version is 4.13.2 or below AND the plugin is actively installed and accessible on a network-reachable WordPress site.

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

Update ProfilePress plugin to the latest version once a patch is released, or apply vendor-supplied security updates. Review access logs and user accounts for any unauthorized access indicators.

Recommended fix High confidence

4.13.3

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find ProfilePress in the plugin list
  4. If an update is available, click 'Update Now' to update to version 4.13.3 or later
  5. Alternatively, go to Dashboard > Updates and select ProfilePress to update
  6. After updating, verify the plugin version shows 4.13.3 or higher under Plugins > Installed Plugins
  7. Test critical user flows (registration, login, membership access) to confirm functionality

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

Fix this in Profilepress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44150 — 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-44150 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