Booking PackageWordPress extension · Saasproject
CVE-2023-39918
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in SAASPROJECT Booking Package Booking Package plugin <= 1.6.01 versions.
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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the Booking Package plugin for WordPress allows attackers to inject malicious scripts via unsanitized input that gets reflected back to the user in the response.
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
Booking PackageWordPress extension
< 1.6.02CVSS 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.1/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 Booking Package plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Package' in the listAffected if the plugin appears in the installed plugins list
-
Check installed version numberIn Plugins list, click on 'Booking Package' to view the plugin details, or check the plugin files in /wp-content/plugins/booking-package/ for a version fileAffected if the displayed version is below 1.6.02 (for example, 1.6.0, 1.5.x, etc.)
-
Identify if the plugin handles user input via URL parametersReview HTTP requests to the site and check if Booking Package processes GET or POST parameters that could be reflected in responses (common vectors include search, id, or action parameters)Affected if the plugin processes parameters from the URL without apparent sanitization
You are affected if Booking Package plugin version is below 1.6.02 and your site processes requests that trigger the plugin's reflected input handling.
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.
dbcve · scoped1.6.02
Update Booking Package plugin to a version newer than 1.6.01; alternatively, implement proper input validation and output encoding on the affected parameters at the web application layer until the patch is applied.
1.6.02
- Backup your WordPress site before making any changes
- Update the Booking Package plugin to version 1.6.02 or later through the WordPress admin dashboard or via wp-cli plugin update command
- Verify the update was successful by checking the installed plugins page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Booking Package
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39918 — 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-2023-39918 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