dbcve.org
Twitter ButtonWordPress extension · Bestwebsoft

CVE-2017-18505

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-12
Fix available
A fix is available. Upgrade to 2.55 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 twitter-plugin plugin before 2.55 for WordPress has XSS.

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

This is a Cross-Site Scripting (XSS) vulnerability in the twitter-plugin for WordPress, affecting all versions prior to 2.55. The vulnerability allows attackers to inject malicious scripts into web pages that are then executed in the browsers of users viewing the affected content.

MitigationUpdate the twitter-plugin to version 2.55 or later to remediate this XSS 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
Twitter ButtonWordPress extension
Affected:< 2.55

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. Confirm WordPress installation
    Verify that the site is running WordPress by checking for wp-content/plugins/ directory or accessing the WordPress admin dashboard.
    Affected if Not applicable - this establishes context for the plugin check.
  2. Check if Bestwebsoft Twitter Button plugin is installed
    Navigate to WordPress admin > Plugins page, or inspect the file system at wp-content/plugins/twitter-button/ to confirm the plugin is present.
    Affected if The plugin must be installed for the vulnerability to apply.
  3. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Bestwebsoft Twitter Button and read the version number displayed. Alternatively, check the plugin's main PHP file for a 'Version' header comment in the plugin metadata.
    Affected if Not applicable - this step retrieves the version for comparison.
  4. Compare installed version to affected range
    Take the version identified in step 3 and compare it against the affected range: versions prior to 2.55 (e.g., 2.54, 2.5, 2.0, 1.x) are affected.
    Affected if The installed version is less than 2.55 - the site is vulnerable to XSS.

The environment is affected if the Bestwebsoft Twitter Button plugin is installed with any version prior to 2.55.

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

Update the twitter-plugin to version 2.55 or later to remediate this XSS vulnerability.

Fix this in Twitter Button 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 the upgrade done

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-2017-18505 — 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-18505 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