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

CVE-2026-6910

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-09
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 6 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 Bookero.pl – system rezerwacji online plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `bookero_products` shortcode's `hide_products` (and `filter_products`) attributes in versions up to and including 2.2. This is due to insufficient input sanitization and output escaping in the `bookero_products()` function — the raw attribute value is concatenated directly into an inline `<script>` block without any escaping. This makes it possible for authenticated attackers with contributor-level access and above to inject arbitrary web scripts into pages that will execute whenever a user accesses the 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 Bookero.pl WordPress plugin versions up to 2.2 contains a stored XSS vulnerability in the bookero_products shortcode. The hide_products and filter_products attributes are not sanitized on input and are directly concatenated into an inline <script> block without output escaping, allowing authenticated contributor+ users to inject arbitrary JavaScript.

MitigationUpgrade to a patched version of the plugin that properly sanitizes shortcode attributes on input and escapes output when constructing inline scripts. If no patch exists, implement output escaping using wp_json_encode() or similar when inserting values into JavaScript context.

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 Bookero plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and locate Bookero.pl. Note the version number displayed under the plugin name.
    Affected if The plugin is installed and the version is 2.2 or lower
  2. Check for shortcode usage
    Search your WordPress database or content pages for the [bookero_products] shortcode. Use phpMyAdmin or WP CLI: wp shortcode list --format=count or search post_content in wp_posts table for 'bookero_products'.
    Affected if The shortcode is present in any post, page, or widget content
  3. Identify vulnerable attributes in use
    Examine posts containing [bookero_products] and check if hide_products or filter_products attributes are present, for example: [bookero_products hide_products="..."].
    Affected if Either hide_products or filter_products attributes are used with any value in the shortcode
  4. Review contributor role access
    In WordPress admin, go to Users > Users and note which users have Contributor, Author, Editor, or Administrator roles. Contributors and above can create content with shortcodes.
    Affected if There are users with Contributor, Author, or higher roles who can create or edit content
  5. Confirm script output context
    View the source HTML of a page containing the bookero_products shortcode. Look for inline <script> tags where shortcode attribute values appear unescaped.
    Affected if The shortcode outputs inline JavaScript with raw values from hide_products or filter_products attributes visible in the HTML source

You are affected if the Bookero plugin version is 2.2 or lower, the bookero_products shortcode with hide_products or filter_products attributes is in use, and users with Contributor or higher roles exist on the site.

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

Upgrade to a patched version of the plugin that properly sanitizes shortcode attributes on input and escapes output when constructing inline scripts. If no patch exists, implement output escaping using wp_json_encode() or similar when inserting values into JavaScript context.

Recommended fix Moderate confidence

Latest version available in the WordPress plugin repository (newer than 2.2)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Bookero.pl – system rezerwacji online' plugin
  4. Check if an update is available and upgrade to the latest version (newer than 2.2)
  5. Verify the update was successful by checking the plugin version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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