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

CVE-2026-1607

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Surbma | Booking.com Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `surbma-bookingcom` shortcode in all versions up to, and including, 2.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, 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 Surbma | Booking.com Shortcode plugin for WordPress contains a stored XSS vulnerability in its shortcode handler. The `surbma-bookingcom` shortcode fails to sanitize user-supplied attributes and escape output, allowing authenticated contributors+ to inject malicious JavaScript that executes when pages containing the shortcode are accessed.

MitigationUpdate the plugin to a patched version once available. Until then, review shortcode usage on the site and consider removing or restricting the shortcode to trusted users only, as the vulnerability can be exploited by any contributor-level account.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Surbma | Booking.com Shortcode' in the list. Alternatively, check the wp-content/plugins directory for a folder named 'surbma-bookingcom' or similar.
    Affected if The plugin is present and active on the WordPress site
  2. Identify shortcode usage in content
    Search the WordPress database (wp_posts table) for occurrences of the shortcode [surbma-bookingcom] using a database query or the WordPress admin search. Check posts, pages, and custom post types.
    Affected if The shortcode [surbma-bookingcom] is present in any published content
  3. Inspect shortcode attributes for unsanitized input
    Examine any existing shortcode instances in content. Look for custom attributes added to the shortcode, such as [surbma-bookingcom attribute="value"], and verify if those values contain special characters like < > " ' that could indicate injection attempts.
    Affected if The shortcode contains custom attributes with unsanitized or potentially malicious values
  4. Review contributor-level user accounts
    In WordPress admin, go to Users and check for accounts with the Contributor role. Contributor users can create and edit their own posts but cannot publish without approval.
    Affected if There are one or more contributor-level users who have authored or can author content containing the shortcode

A user is affected if the plugin is installed, the shortcode is used in any content, and any contributor-level account exists on the site, since the XSS can be injected through shortcode attributes by authenticated contributors.

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 the plugin to a patched version once available. Until then, review shortcode usage on the site and consider removing or restricting the shortcode to trusted users only, as the vulnerability can be exploited by any contributor-level account.

Recommended fix Moderate confidence

Latest version available on wordpress.org (after 2.1)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Surbma | Booking.com Shortcode' plugin
  3. 3. Check if an update is available. If so, update to the latest version which should contain the fix for the stored XSS vulnerability
  4. 4. Alternatively, navigate to Plugins > Add New > Upload Plugin to manually upload the updated version if available on wordpress.org
  5. 5. After updating, verify that the shortcode attributes are properly sanitized by testing with a non-malicious value first
  6. 6. Clear any caching plugins if used to ensure the patched version is served

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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 locally
dbcve dependency scanner

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