dbcve.org
Wp Social Login And Register Social CounterWordPress extension · Wpmet

CVE-2022-47160

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Wpmet Wp Social Login and Register Social Counter.This issue affects Wp Social Login and Register Social Counter: from n/a through 1.9.0.

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

This is an information disclosure vulnerability in the Wpmet WP Social Login and Register Social Counter WordPress plugin affecting all versions through 1.9.0. The vulnerability allows unauthorized actors to access sensitive information, likely related to OAuth tokens, social API credentials, or user session data handled by the social login functionality.

MitigationUpdate the plugin to version 1.9.1 or later to patch the information disclosure vulnerability. After updating, verify that social login functionality continues to work correctly and that no sensitive data is exposed.

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
Wp Social Login And Register Social CounterWordPress extension
Affected:< 2.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Wpmet WP Social Login and Register Social Counter', or use 'wp plugin list' via WP-CLI, or inspect the plugin main file header in wp-content/plugins/wp-social-logi*/index.php for the Version comment
    Affected if The version listed is below 2.0.0 (or 1.9.0, if the fix was indeed in 1.9.1 per the summary)
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin is activated. If it is installed but deactivated, the vulnerability is not reachable
    Affected if Plugin shows as Active
  3. Check if social login is configured
    Go to plugin settings (usually under Settings > WP Social Login or similar) and look for configured OAuth credentials, API keys, or social platform connections (Facebook, Google, etc.)
    Affected if Any social login provider is connected with API credentials stored in the database
  4. Inspect for exposed sensitive data
    Check the plugin directory (wp-content/plugins/wp-social-logi*/) for any publicly accessible files that may output stored credentials, tokens, or user session data. Look for any wp-admin-ajax.php or custom endpoints that may leak sensitive information without authentication
    Affected if Accessing specific plugin URLs returns OAuth tokens, API secrets, or user data in the response

If the plugin version is below 2.0.0, the plugin is active, and social login is configured with API credentials, the environment is likely affected by this information disclosure vulnerability.

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 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Update the plugin to version 1.9.1 or later to patch the information disclosure vulnerability. After updating, verify that social login functionality continues to work correctly and that no sensitive data is exposed.

Recommended fix High confidence

Version 2.0.0 or later of Wp Social Login And Register Social Counter (Wpmet)

  1. 1. Back up your WordPress site database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'Wp Social Login And Register Social Counter' in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to version 2.0.0 or later
  5. 5. Alternatively, manually upload the version 2.0.0+ plugin files via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 2.0.0 or higher in the plugins list
  7. 7. Test that social login functionality still works correctly
Caveat Review plugin settings after upgrade as minor configuration changes may have occurred between versions

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

Fix this in Wp Social Login And Register Social Counter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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