Skip to main content
Vulnerability Database/CVE-2026-78001

CVE-2026-78001: BoldGrid WordPress Plugin XSS Vulnerability

CVE-2026-78001 is a stored XSS vulnerability in the BoldGrid Visual Drag and Drop Editor WordPress plugin affecting versions up to 1.27.13. Attackers with Contributor access can inject malicious scripts. This article covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-78001 Overview

CVE-2026-78001 affects the Post and Page Builder by BoldGrid – Visual Drag and Drop Editor plugin for WordPress. The vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the Table Designer feature, specifically within the data-label attribute handling. All plugin versions up to and including 1.27.13 are affected due to insufficient input sanitization and output escaping. Authenticated users with Contributor-level access or above can inject arbitrary JavaScript that executes when any visitor loads an affected page. The issue is tracked under [CWE-79] (Improper Neutralization of Input During Web Page Generation).

Critical Impact

Authenticated contributors can inject persistent JavaScript executed in the browsers of any user viewing a crafted page, enabling session theft, admin account takeover, and arbitrary redirection.

Affected Products

  • Post and Page Builder by BoldGrid – Visual Drag and Drop Editor (WordPress plugin)
  • All plugin versions up to and including 1.27.13
  • Fixed in version 1.27.14

Discovery Timeline

  • 2026-10-15 - CVE-2026-78001 published to the National Vulnerability Database (NVD)
  • 2026-10-15 - Last updated in the NVD database

Technical Details for CVE-2026-78001

Vulnerability Analysis

The vulnerability resides in the Table Designer component of the BoldGrid Post and Page Builder plugin. The plugin accepts user-supplied content for the data-label HTML attribute without properly sanitizing input or escaping output when the stored content is rendered. An attacker with Contributor permissions or higher can craft a table in a page or post and inject JavaScript payloads into the data-label value. When the page is viewed by other users, including administrators, the injected script executes in their browser context under the site's origin.

Stored XSS in a WordPress page builder is particularly impactful because low-privilege authors routinely submit content that administrators and editors review. The CVSS scope change (S:C) in the vector reflects that script execution crosses the trust boundary from the authenticated authoring context into any visitor's browser session.

Root Cause

The root cause is missing input validation on the data-label field server-side and absent output escaping when the stored table markup is emitted into page HTML. Expected behavior would call WordPress sanitization helpers such as sanitize_text_field() on input and esc_attr() on output for attribute contexts. The fix landed in changeset 3674803 for plugin version 1.27.14.

Attack Vector

Exploitation requires an authenticated session with at least Contributor privileges. The attacker creates or edits a page using the Table Designer, injects a payload into the data-label attribute, and submits the page. When an administrator previews or publishes the content, or when any visitor accesses the published page, the payload executes. Impact includes cookie theft, forced administrative actions through forged requests, plugin backdoor installation, and visitor redirection to attacker-controlled infrastructure.

See the Wordfence Vulnerability Report #23049 and the WordPress Plugin Changeset Update for the patch diff.

Detection Methods for CVE-2026-78001

Indicators of Compromise

  • Table elements in wp_posts content containing data-label attribute values with <script>, onerror, onload, or javascript: substrings.
  • Unexpected outbound requests from administrator browsers to unfamiliar domains following page previews or edits.
  • New administrator accounts or modified user roles created shortly after a Contributor submitted or updated a page.
  • Unauthorized changes to plugin or theme files triggered from administrator sessions.

Detection Strategies

  • Query the WordPress database for stored table markup containing suspicious attribute content: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%data-label=%<script%';.
  • Review audit logs for pages created or edited by Contributor-level accounts that were later viewed by administrators.
  • Monitor browser Content Security Policy (CSP) violation reports for inline script execution originating from /wp-content/ rendered pages.

Monitoring Recommendations

  • Enable WordPress activity logging to track content changes by low-privilege roles.
  • Forward web server and WordPress logs to a centralized analytics platform to correlate authoring events with downstream administrator sessions.
  • Alert on creation of new administrator accounts, role changes, and plugin installations following suspicious page submissions.

How to Mitigate CVE-2026-78001

Immediate Actions Required

  • Update the Post and Page Builder by BoldGrid plugin to version 1.27.14 or later on all WordPress sites.
  • Audit existing pages and posts for malicious data-label attribute content and remove any injected scripts.
  • Review Contributor, Author, and Editor accounts for unexpected activity and reset credentials where suspicious changes are observed.
  • Rotate administrator session cookies and secret keys defined in wp-config.php if compromise is suspected.

Patch Information

The vendor addressed the vulnerability in version 1.27.14 via changeset 3674803. The patch adds proper sanitization of input and escaping of the data-label attribute when rendering table markup. Refer to the WordPress Plugin Changeset Update for the exact code changes.

Workarounds

  • Restrict Contributor-level and higher privileges to trusted users only until the patch is applied.
  • Temporarily disable the Post and Page Builder plugin on sites where immediate patching is not feasible.
  • Deploy a Web Application Firewall (WAF) rule to block requests containing data-label attribute values with script-related tokens.
  • Enforce a strict Content Security Policy that disallows inline scripts to reduce the impact of stored XSS payloads.
bash
# Update the plugin using WP-CLI
wp plugin update post-and-page-builder --version=1.27.14

# Verify installed version
wp plugin get post-and-page-builder --field=version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.