dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-34077

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
An authentication bypass vulnerability exists in the WordPress Pie Register plugin ≤ 3.7.1.4 that allows unauthenticated attackers to impersonate arbitrary users by submitting a crafted POST request to the login endpoint. By setting social_site=true and manipulating the user_id_social_site parameter, an attacker can generate a valid WordPress session cookie for any user ID, including administrators. Once authenticated, the attacker may exploit plugin upload functionality to install a malicious plugin containing arbitrary PHP code, resulting in remote code execution on the underlying server.

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 WordPress Pie Register plugin versions 3.7.1.4 and below contains an authentication bypass vulnerability where unauthenticated attackers can craft POST requests to the login endpoint with social_site=true and a manipulated user_id_social_site parameter. This allows generation of valid WordPress session cookies for arbitrary user IDs, including administrators, enabling full account impersonation.

MitigationUpdate the Pie Register plugin to the latest patched version immediately. If immediate update is not possible, disable the plugin or implement WAF rules to block suspicious POST requests to the login endpoint with the social_site parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Pie Register plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Pie Register. Check the version number displayed. Alternatively, check the plugin file /wp-content/plugins/pie-register/readme.txt for the Version header, or query the WordPress database in wp_options for option_name 'pie_register_version'.
    Affected if The installed version is 3.7.1.4 or lower.
  2. Confirm if social login feature is enabled
    In WordPress admin, navigate to Pie Register settings. Look for social login or social connect configuration pages. Check if any social providers (Google, Facebook, etc.) are enabled. In the database, query wp_options for options containing 'social' or 'pie_register_social' in the name.
    Affected if Social login functionality is enabled for any provider.
  3. Audit WordPress user accounts for unauthorized additions or modifications
    In WordPress admin, go to Users > All Users. Review the list for unknown administrator accounts, recently added users, or users with altered roles. Query the wp_users and wp_usermeta tables to check for user creation dates and role assignments, focusing on accounts created around the time of potential exploitation.
    Affected if Unexpected administrator accounts exist or user roles were modified without authorization.
  4. Inspect for unauthorized plugin uploads
    In WordPress admin, go to Plugins > Installed Plugins. Look for unfamiliar or suspicious plugins, especially those without known authors or with unusual names. Check the /wp-content/plugins/ directory for recently added folders. Query wp_options for option_name 'active_plugins' to compare against known legitimate plugins.
    Affected if Unknown or malicious plugins are present that were not intentionally installed.
  5. Review server logs for suspicious login POST requests
    Examine web server access logs (Apache error.log, Nginx access.log) or WordPress debug logs for POST requests to the login endpoint (/wp-login.php or /?page=pie-register) containing the parameters 'social_site=true' and 'user_id_social_site'. Search for requests with unusual user IDs or from unexpected IP addresses.
    Affected if Log entries show POST requests with social_site parameter set to true and manipulated user_id_social_site values.

A user is affected if Pie Register version 3.7.1.4 or lower is installed with social login enabled, or if unauthorized admin accounts, plugins, or suspicious login requests are detected in the environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Pie Register plugin to the latest patched version immediately. If immediate update is not possible, disable the plugin or implement WAF rules to block suspicious POST requests to the login endpoint with the social_site parameter.

Recommended fix Moderate confidence

Latest Pie Register version available on wordpress.org (verify version > 3.7.1.4 contains the security fix)

  1. 1. Immediately disable the Pie Register plugin if not needed, or restrict access to the wp-login.php and registration endpoints using web server configuration (e.g., .htaccess IP blocking or auth requirements).
  2. 2. Check the current installed version of Pie Register plugin in WordPress admin under Plugins > Installed Plugins.
  3. 3. Navigate to Plugins > Add New > Upload Plugin (or check wordpress.org for the latest version).
  4. 4. Download and install the latest version of Pie Register from the official WordPress repository.
  5. 5. After upgrading, verify that the social_site authentication bypass is no longer functional by reviewing plugin code changes or release notes for security fixes.
  6. 6. Review user accounts for any unauthorized admin accounts created after the vulnerability disclosure date.
  7. 7. Rotate all WordPress passwords and session tokens as a precautionary measure.
Caveat Review plugin changelog for any settings or functionality changes between 3.7.1.4 and the new version

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

Have this fixed 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 help mitigating

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-2025-34077 — 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-2025-34077 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