dbcve.org
Social LoginWordPress extension · Bestwebsoft

CVE-2017-18501

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-12
Fix available
A fix is available. Upgrade to 0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
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
The social-login-bws plugin before 0.2 for WordPress has multiple XSS issues.

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

The social-login-bws plugin before version 0.2 for WordPress contains multiple Cross-Site Scripting (XSS) vulnerabilities. These allow attackers to inject malicious scripts into web pages viewed by users of the plugin, potentially compromising user sessions or stealing credentials.

MitigationUpdate the social-login-bws plugin to version 0.2 or later. If an update is unavailable, remove the plugin entirely to eliminate the vulnerability.

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 LoginWordPress extension
Affected:< 0.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Locate the social-login-bws plugin files
    Check your WordPress installation's /wp-content/plugins/ directory for a folder named 'social-login-bws' or similar. Use file explorer, FTP, or SSH to list the plugin directory.
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin file (typically social-login-bws.php or similar in the plugin folder) and locate the version comment/header at the top of the file. Alternatively, check the WordPress admin under Plugins > Installed Plugins and look for the Bestwebsoft Social Login entry.
    Affected if The version shown is less than 0.2 (e.g., 0.1, or no version displayed)
  3. Verify the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check if Bestwebsoft Social Login is currently activated. Alternatively, query the wp_options table for option_name 'active_plugins' and check if the social-login-bws plugin is included.
    Affected if The plugin is activated and running

Your environment is affected if the Bestwebsoft Social Login plugin is installed, active, and running a version numbered below 0.2.

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.

From vendor data
Upgrade available Upgrade to 0.2 or later
Fixed in 0.2
Interim mitigation

Update the social-login-bws plugin to version 0.2 or later. If an update is unavailable, remove the plugin entirely to eliminate the vulnerability.

Fix this in Social Login Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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