dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6818

HIGH · 7.2 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 VikBooking Hotel Booking Engine & PMS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'special_requests' 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 confidence

The VikBooking Hotel Booking Engine & PMS WordPress plugin up to version 1.8.8 contains a stored XSS vulnerability in the 'special_requests' parameter. Due to insufficient input sanitization on submission and lack of output escaping on display, unauthenticated attackers can inject arbitrary JavaScript that persists in the database and executes when administrators or staff view booking records.

MitigationUpdate VikBooking to version 1.8.9 or later which addresses the sanitization and escaping gaps. Until patched, avoid accessing booking pages or implement WAF rules to filter malicious requests.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm VikBooking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'VikBooking Hotel Booking Engine & PMS'. Note whether it is active.
    Affected if The plugin is installed and active, exposing the booking functionality.
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find VikBooking, and read the version number displayed beneath the plugin name. Compare this to the affected range: versions up to 1.8.8 are vulnerable, version 1.8.9 and later are fixed.
    Affected if The installed version is 1.8.8 or lower.
  3. Verify the booking form is publicly accessible
    Visit the page on your website where the VikBooking reservation form is displayed (typically a page with shortcode [vikbooking] or a dedicated booking page). Attempt to complete a test booking and locate the 'special_requests' or similar free-text field.
    Affected if The booking form is publicly accessible and accepts user input in the special_requests field.
  4. Inspect database for suspicious stored content
    Access your WordPress database via phpMyAdmin or command line. Query the bookings table (commonly prefix_vikbooking_bookings or similar) and examine the special_requests column for unexpected HTML tags, script tags, or JavaScript event handlers.
    Affected if The database contains unsanitized HTML or script tags in the special_requests field that could execute when viewed.

You are affected if the VikBooking plugin is installed with version 1.8.8 or lower, the booking form is publicly accessible, and malicious scripts have been injected into the special_requests field in the database.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update VikBooking to version 1.8.9 or later which addresses the sanitization and escaping gaps. Until patched, avoid accessing booking pages or implement WAF rules to filter malicious requests.

Recommended fix Moderate confidence

latest version above 1.8.8

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'VikBooking Hotel Booking Engine & PMS'
  4. Check if an update is available and update to the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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