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

CVE-2026-8702

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
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 GBI To Print plugin for WordPress is vulnerable to Stored Cross-Site Scripting in version 1.0 via the 'div' attribute of the 'gbitoprint' shortcode. This is due to insufficient output escaping in the gbi_toprint_shortcode() function, which concatenates the raw shortcode attribute value directly into an HTML attribute without applying esc_attr() or any other sanitization. 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 GBI To Print WordPress plugin v1.0 contains a stored XSS vulnerability in the gbi_toprint_shortcode() function. The 'div' attribute from the [gbitoprint] shortcode is directly concatenated into an HTML attribute without sanitization (missing esc_attr()), allowing authenticated contributors+ to inject malicious JavaScript that executes when users view affected pages.

MitigationApply output escaping using esc_attr() to the 'div' attribute before rendering it in HTML. Verify all other shortcode attributes are also properly escaped.

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. Confirm plugin installation and version
    Navigate to WordPress Admin > Plugins and locate 'GBI To Print'. Verify the version column shows v1.0. Alternatively, check the plugin main file header for 'Version: 1.0'.
    Affected if The plugin is installed and the version is 1.0 exactly (or if version cannot be determined and the plugin is present, assume affected)
  2. Identify shortcode usage
    Search the WordPress database or site content for instances of '[gbitoprint]' shortcode. Use WP Admin > Posts > All Posts and Pages, or query the wp_posts table for post_content containing 'gbitoprint'.
    Affected if The [gbitoprint] shortcode is present in any post, page, or widget content
  3. Inspect the div attribute usage
    Examine each found shortcode instance to see if it includes a 'div' attribute, for example: [gbitoprint div='value']. If the shortcode is used without any attributes, it may not be vulnerable.
    Affected if The shortcode is used with a 'div' attribute present
  4. Verify the vulnerability in plugin code
    Access the plugin file containing gbi_toprint_shortcode() function (typically in the main plugin file). Search for the line where the 'div' attribute is rendered into HTML. Look for missing esc_attr() wrapper around the div attribute value.
    Affected if The code directly outputs the div attribute value without esc_attr() or similar sanitization
  5. Check for injected scripts in affected pages
    View pages containing the vulnerable shortcode in a browser. Inspect the page source and look for the rendered div element. Use browser DevTools to check if unexpected script tags or event handlers (onerror, onload, etc.) appear within the div's HTML attributes.
    Affected if Unexpected JavaScript executes or appears in the page source when viewing pages with the shortcode

You are affected if the GBI To Print plugin v1.0 is installed AND the [gbitoprint] shortcode with a 'div' attribute is used on your site, as the unsanitized attribute allows script injection.

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

Apply output escaping using esc_attr() to the 'div' attribute before rendering it in HTML. Verify all other shortcode attributes are also properly escaped.

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-8702 — 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-8702 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