PinterestWordPress extension · Bestwebsoft
CVE-2017-18517
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 · uneditedThe bws-pinterest plugin before 1.0.5 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 · high confidenceThe bws-pinterest WordPress plugin before version 1.0.5 contains multiple Cross-Site Scripting (XSS) vulnerabilities. XSS flaws allow attackers to inject malicious scripts into web pages viewed by other users, potentially stealing session cookies, credentials, or performing actions on behalf of victims.
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
PinterestWordPress extension
< 1.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify bws-priority plugin is installedLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Pinterest' or 'bws-pinterest' in the list of active and inactive plugins.Affected if The plugin named 'Bestwebsoft Pinterest' or containing 'bws-pinterest' appears in the plugin list.
-
Check installed plugin versionIn the Plugins list, locate the bws-pinterest plugin and hover over or click on the plugin name to reveal the version number, or click on the plugin details link to view the version information.Affected if A version number is displayed that is below 1.0.5 (for example, 1.0.4, 1.0.3, 1.0.2, etc.).
-
Inspect plugin directory version fileAccess the WordPress site via FTP or file manager, navigate to wp-content/plugins/bws-pinterest/, and open the main plugin PHP file (often named bws-pinterest.php or similar) to find the version defined in the plugin header comments.Affected if The version constant or header declares a version lower than 1.0.5.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify whether the bws-pinterest plugin is currently activated. Check both the Active and Inactive plugin lists.Affected if The plugin is listed as Active and the version is below 1.0.5.
If the bws-pinterest plugin is installed and active with a version number less than 1.0.5, the environment is affected by the CVE-2017-18517 XSS vulnerabilities.
Generated from the published advisory. Verify against your own configuration.
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 data1.0.5
Update the bws-pinterest plugin to version 1.0.5 or later to remediate the XSS vulnerabilities. If updating is not possible, consider removing the plugin until a fix can be applied.
Fix this in Pinterest
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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