PromobarWordPress extension · Bestwebsoft
CVE-2017-18529
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 promobar plugin before 1.1.1 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 promobar WordPress plugin before version 1.1.1 contains multiple cross-site scripting (XSS) vulnerabilities. These allow authenticated or unauthenticated attackers to inject malicious JavaScript code through the plugin's input fields, potentially compromising other users viewing the affected pages.
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
PromobarWordPress extension
< 1.1.1CVSS 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.
-
Locate the promobar plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'promobar' or 'bestwebsoft-promobar'. Alternatively, navigate to WP Admin > Plugins and search for 'Bestwebsoft Promobar' or 'promobar'.Affected if The plugin folder or entry is not found in the plugins directory, meaning the plugin is not installed.
-
Determine the installed version numberIn WP Admin, go to Plugins > Installed Plugins > Bestwebsoft Promobar and read the version number displayed below the plugin name. If using SSH/CLI, check the main plugin file header (e.g., wp-content/plugins/promobar/promobar.php) for the 'Version' tag.Affected if The version listed is below 1.1.1 (for example, 1.1.0, 1.0.9, etc.).
-
Verify if the plugin is currently activeIn WP Admin > Plugins, check whether Bestwebsoft Promobar shows as 'Active' under the plugin status. If using WP-CLI, run: wp plugin status promobarAffected if The plugin status shows as 'Active', meaning the vulnerable code can be executed.
-
Identify exposed input pointsNavigate to the plugin settings page (usually under WP Admin > Promobar or Settings > Promobar) and inspect any text input fields, color pickers, or toggle options where user-supplied values are saved and displayed on the frontend.Affected if Input fields exist and accept user data without sanitization output, indicating the XSS vector is present.
The environment is affected if the Bestwebsoft Promobar plugin is installed, active, and running at a version lower than 1.1.1, with accessible input fields that accept unsanitized user data.
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.1.1
Update the promobar plugin to version 1.1.1 or later to remediate the XSS vulnerabilities.
Fix this in Promobar
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18529 — 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-18529 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