CVE-2026-6820
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 VikBooking Hotel Booking Engine & PMS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'email' parameter in all versions up to, and including, 1.8.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 VikBooking Hotel Booking Engine & PMS WordPress plugin versions up to 1.8.8 have a stored XSS vulnerability in the email input field. Unauthenticated attackers can inject malicious JavaScript via the email parameter because the plugin lacks proper input sanitization on submission and output escaping when the email is displayed, causing scripts to execute for all users viewing affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Confirm VikBooking plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'VikBooking Hotel Booking Engine & PMS', or check the plugins directory for the VikBooking folderAffected if VikBooking plugin is not installed on the WordPress site
-
Check installed VikBooking versionIn WordPress admin, go to Plugins > Installed Plugins and find the version number listed under VikBooking, or check the main plugin PHP file for the version constantAffected if Version is 1.8.8 or earlier (any version up to and including 1.8.8)
-
Verify booking form is accessibleVisit the frontend booking page where the email input field is presented (typically a booking or reservation form page), or check VikBooking settings under Booking Channels to confirm the form is enabledAffected if The booking form with email input is enabled and publicly accessible to unauthenticated users
User is affected if VikBooking plugin version 1.8.8 or earlier is installed and the booking form with the email input field is enabled and accessible to visitors
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 dataUpdate the VikBooking plugin to version 1.8.9 or later which includes proper input sanitization (sanitize_email() in PHP) and output escaping (esc_html() or esc_attr()) for the email field. If update is not immediately possible, consider disabling the booking form or implementing a Web Application Firewall rule to block malicious email input patterns.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6820 — 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-2026-6820 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