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

CVE-2026-12754

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Reflected Cross-Site Scripting via the 'layoutstyle' parameter in all versions up to, and including, 1.8.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Exploitation requires the targeted page to render the [vikbooking view="roomslist"] shortcode, as the vulnerable layoutstyle parameter is only processed in that view context.

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 is vulnerable to reflected cross-site scripting (XSS) in all versions up to 1.8.12. The vulnerability exists in the 'layoutstyle' parameter within the roomslist view context (triggered by the [vikbooking view='roomslist'] shortcode). Insufficient input sanitization and lack of output escaping allows unauthenticated attackers to inject arbitrary JavaScript via maliciously crafted URLs.

MitigationUpdate the VikBooking plugin to version 1.8.13 or later which contains proper input sanitization and output escaping for the layoutstyle parameter. Until patched, avoid using the roomslist shortcode on publicly accessible pages or implement WAF rules to block malicious 'layoutstyle' parameter values.

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
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 checks

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

  1. Verify VikBooking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'VikBooking Hotel Booking Engine & PMS'. Note the installed version number displayed next to the plugin name.
    Affected if VikBooking plugin is installed with a version of 1.8.12 or lower, or if the version cannot be determined but the plugin is present.
  2. Confirm the exact plugin version
    Check the plugin version in the plugin header file (typically in vikbooking.php) or in the WordPress plugin repository metadata. Compare your version against the affected range: any version up to and including 1.8.12.
    Affected if The installed version is 1.8.12 or earlier.
  3. Identify usage of the roomslist shortcode
    Search your WordPress pages, posts, and widgets for the shortcode [vikbooking view='roomslist'] using the WordPress admin search or by querying the wp_posts database table for that string.
    Affected if The roomslist shortcode is present and publicly accessible on any page on your site.
  4. Test the layoutstyle parameter for XSS vulnerability
    If the roomslist shortcode is in use, access the page and append ?layoutstyle=<script>alert(1)</script> to the URL. If the JavaScript executes, the vulnerability is present.
    Affected if Arbitrary JavaScript executes when a specially crafted layoutstyle parameter is passed in the URL.

You are affected if VikBooking plugin version 1.8.12 or lower is installed AND the roomslist shortcode is used on a publicly accessible page, as this allows reflected XSS via the layoutstyle parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the VikBooking plugin to version 1.8.13 or later which contains proper input sanitization and output escaping for the layoutstyle parameter. Until patched, avoid using the roomslist shortcode on publicly accessible pages or implement WAF rules to block malicious 'layoutstyle' parameter values.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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