dbcve.org
TestimonialsWordPress extension · Bestwebsoft

CVE-2017-18558

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-21
Fix available
A fix is available. Upgrade to 0.1.9 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 bws-testimonials plugin before 0.1.9 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 bws-testimonials WordPress plugin before version 0.1.9 contains multiple Cross-Site Scripting (XSS) vulnerabilities. XSS allows attackers to inject malicious JavaScript into web pages viewed by other users, potentially stealing session cookies, defacing content, or performing actions on behalf of authenticated users.

MitigationUpdate the bws-testimonials plugin to version 0.1.9 or later to remediate the XSS vulnerabilities. If immediate updating is not possible, consider disabling the plugin until a patch can be applied.

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
TestimonialsWordPress extension
Affected:< 0.1.9

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. Check if bws-testimonials plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Bestwebsoft Testimonials' or 'bws-testimonials' in the installed plugins list
    Affected if The plugin appears in the plugins list
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view its details, or check the plugin header in /wp-content/plugins/bws-testimonials/bws-testimonials.php for the 'Version' field
    Affected if The displayed version number is less than 0.1.9 (for example, 0.1.8, 0.1.7, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the plugin has an 'Active' status rather than 'Inactive'
    Affected if The plugin is active and running on the site
  4. Confirm plugin files exist
    Check for the existence of /wp-content/plugins/bws-testimonials/ directory via file manager or FTP access
    Affected if The plugin directory exists on the server

You are affected if the bws-testimonials plugin is installed, active, and the installed version is below 0.1.9, as this version range contains the documented XSS vulnerabilities.

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.1.9 or later
Fixed in 0.1.9
Interim mitigation

Update the bws-testimonials plugin to version 0.1.9 or later to remediate the XSS vulnerabilities. If immediate updating is not possible, consider disabling the plugin until a patch can be applied.

Fix this in Testimonials Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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