Wp Booking SystemWordPress extension · Wpbookingsystem
CVE-2017-2168
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 · uneditedCross-site scripting vulnerability in WP Booking System Free version prior to version 1.4 and WP Booking System Premium version prior to version 3.7 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in the WP Booking System WordPress plugin affecting both Free (prior to 1.4) and Premium (prior to 3.7) versions. The vulnerability allows remote attackers to inject arbitrary web script or HTML through booking system input fields (such as customer details, calendar fields, or booking notes), which then executes when administrators or other users view the booking data in the plugin dashboard.
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
Wp Booking SystemWordPress extension
<= 1.3.3<= 3.6CVSS 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 WP Booking System plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-booking-system' or similarAffected if The plugin is present in the WordPress installation
-
Identify the installed versionIn WordPress admin, go to Plugins > Installed Plugins and find WP Booking System. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a 'Version' header commentAffected if Version is 1.3.3 or lower for Free version, or 3.6 or lower for Premium version
-
Confirm plugin type (Free or Premium)Check the plugin name displayed in the plugins list - it may indicate 'Free' or 'Premium', or inspect the plugin files for license indicatorsAffected if Running the Free version <= 1.3.3 or Premium version <= 3.6
-
Check if booking data exists in the databaseAccess WordPress database via phpMyAdmin or command line and query the plugin's booking tables (typically wp_wpbs_bookings or similar naming convention) for any stored booking entriesAffected if Booking records exist and could potentially contain malicious script payloads
You are affected if WP Booking System Free version <= 1.3.3 or Premium version <= 3.6 is installed and active, with booking data present that could contain injected XSS payloads.
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 dataUpgrade to WP Booking System Free version 1.4 or Premium version 3.7 or later, which contain proper input sanitization and output escaping to neutralize malicious script injection.
Fix this in Wp Booking System
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2168 — 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-2168 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