dbcve.org
ProfilepressWordPress extension · Properfraction

CVE-2024-9947

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 4.11.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The ProfilePress Pro plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.11.1. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.

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 confidence

The ProfilePress Pro WordPress plugin has an authentication bypass vulnerability in its social login functionality. The plugin fails to properly verify the user identity returned by the social login token, allowing unauthenticated attackers to authenticate as any existing user (including administrators) by knowing their email address and leveraging the flawed token validation.

MitigationUpdate ProfilePress Pro to version 4.11.2 or later. If immediate updates are not possible, disable the social login feature and review administrative user accounts for suspicious activity.

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.11.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the installed ProfilePress Pro version
    Navigate to WordPress Admin > Plugins > Installed Plugins. Locate 'ProfilePress Pro' (or 'ProfilePress' with Pro indicator) and read the version number displayed. Alternatively, inspect the plugin's main PHP file (commonly /wp-content/plugins/profilepress-pro/classes/version.php or similar) to read the 'Version' header comment.
    Affected if The version displayed is earlier than 4.11.2 (for example, 4.11.1, 4.10.x, or older).
  2. Verify if social login is enabled
    Go to ProfilePress settings in WordPress admin. Look for a section labeled 'Social Login', 'Social Integration', or similar. Check if any social login providers (such as Google, Facebook, Twitter/X, LinkedIn, or others) are configured and the feature is toggled on or active.
    Affected if One or more social login providers are enabled and configured in the plugin settings.
  3. Inspect social login token handling settings
    Within the ProfilePress social login settings panel, review any options related to token validation, 'Skip Email Verification', or 'Auto Register Users'. Look for settings that control how the plugin processes the identity token returned by the social provider.
    Affected if Token validation is disabled or set to bypass, or automatic user registration without email verification is enabled.
  4. Review administrative user accounts for unauthorized access
    Navigate to WordPress Admin > Users. Examine the list of administrators and other users. Look for any unfamiliar admin accounts, or check user metadata and login logs (via WordPress activity logs or security plugins) for suspicious admin logins from unknown IP addresses, especially around the time the vulnerability became public.
    Affected if New or unexpected administrator accounts exist, or admin login activity shows sessions from IP addresses you do not recognize.

You are affected if the ProfilePress Pro version is earlier than 4.11.2 AND the social login feature is currently enabled in your WordPress installation.

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.11.2 or later
Fixed in 4.11.2
Interim mitigation

Update ProfilePress Pro to version 4.11.2 or later. If immediate updates are not possible, disable the social login feature and review administrative user accounts for suspicious activity.

Recommended fix High confidence

ProfilePress Pro 4.11.2

  1. Create a full backup of your WordPress site (database and files) before updating
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find ProfilePress (or ProfilePress Pro) in the installed plugins list
  4. Click 'Update now' or navigate to the plugin update interface
  5. Update ProfilePress to version 4.11.2
  6. Verify the update completed successfully by checking the plugin version
  7. Confirm the site functionality remains intact after the update

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

Fix this in Profilepress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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