CVE-2026-8702 MEDIUM

CVE-2026-8702: GBI To Print <= 1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'div' Shortcode Attribute

Vendor Garber
Product GBI To Print
Weakness CWE-79 · XSS
Published May 27, 2026
Last update May 27, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

GBI To Print versions 1.0 and earlier contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts. The vulnerability has changed scope, meaning injected code can affect other users or site functionality beyond the vulnerable component. An attacker with low-level account access can craft malicious input that executes in other users' browsers without requiring additional user interaction.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that execute in other users' browsers and affect site functionality.

Potential impact on your site

04Site Impact

Authenticated users can inject scripts affecting other users' sessions, potentially stealing data or modifying site behavior.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account on the site; no user interaction required.

Key dates

06Disclosure timeline

May 27, 2026 CVE published
May 27, 2026 Record updated