dbcve.org
Social Login WpWordPress extension · Social Login Wp Project

CVE-2022-38063

HIGH · 8.8 CVSS v3.1 Published 2023-03-16
Fix available
A fix is available. Upgrade to after 5.0.0.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Social Login WP plugin <= 5.0.0.0 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Social Login WP WordPress plugin versions 5.0.0.0 and earlier allows attackers to perform unauthorized actions on behalf of authenticated users by tricking them into clicking malicious links or visiting compromised pages. The lack of proper anti-CSRF token validation in the plugin's forms or AJAX actions enables attackers to potentially manipulate user authentication settings or perform actions in the context of logged-in users.

MitigationUpdate the Social Login WP plugin to the latest patched version. If no update is available, manually add WordPress nonce verification (wp_nonce_field and wp_verify_nonce) to all form submissions and AJAX actions within the plugin.

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
Social Login WpWordPress extension
Affected:<= 5.0.0.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Social Login WP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Social Login WP' or 'Social Login Wp Project Social Login Wp'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'social-login-wp' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find Social Login WP and view the version number under the plugin name. Compare against <= 5.0.0.0
    Affected if The installed version is 5.0.0.0 or lower
  3. Inspect plugin for missing nonce verification
    Access the WordPress site via FTP or file manager, navigate to wp-content/plugins/social-login-wp (or the plugin folder name), and search plugin PHP files for 'wp_nonce_field' or 'wp_verify_nonce'. Use grep or a text editor to search for these nonce functions.
    Affected if The plugin forms or AJAX action handlers lack wp_nonce_field in form output or wp_verify_nonce in processing code
  4. Identify exposed vulnerable forms or AJAX endpoints
    Examine the plugin's main PHP files for form tags (look for <form) and AJAX handlers (look for add_action('wp_ajax_') or 'admin_post_'). Check if these handlers validate user identity before processing requests.
    Affected if Forms submit to admin-post.php or AJAX endpoints without verifying a nonce token before processing sensitive actions

A user is affected if the Social Login WP plugin version 5.0.0.0 or lower is installed AND the plugin's forms or AJAX actions do not implement WordPress nonce validation (wp_nonce_field and wp_verify_nonce).

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 a release after 5.0.0.0
Interim mitigation

Update the Social Login WP plugin to the latest patched version. If no update is available, manually add WordPress nonce verification (wp_nonce_field and wp_verify_nonce) to all form submissions and AJAX actions within the plugin.

Recommended fix Moderate confidence

Latest available version of Social Login WP (check WordPress plugin repository for current stable release)

  1. Check WordPress admin dashboard for plugin updates under Plugins > All Plugins
  2. Locate 'Social Login WP' plugin in the plugins list
  3. If an update is available, click 'Update Now' to install the latest version
  4. After updating, verify the new version number reflects the patch (check plugin details or changelog)
  5. Test the Social Login functionality to ensure it works correctly after the update

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

Fix this in Social Login Wp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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