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-107758 Overview
The Colibri Page Builder plugin for WordPress contains a stored Cross-Site Scripting (XSS) vulnerability [CWE-79] affecting all versions up to and including 1.0.390. The flaw resides in the handling of the comment parameter, where insufficient input sanitization and output escaping allow unauthenticated attackers to inject arbitrary JavaScript. Injected payloads persist in storage and execute whenever any user loads an affected front-end page. The vulnerability combines a permissive KSES allow-list for SVG elements with a client-side script that decodes and evaluates attacker-controlled HTML.
Critical Impact
Unauthenticated attackers can inject persistent JavaScript that executes in every visitor's browser, enabling session theft, account takeover, and site defacement.
Affected Products
- Colibri Page Builder plugin for WordPress
- All versions up to and including 1.0.390
- WordPress sites with the plugin enqueueing colibri.js globally on front-end pages
Discovery Timeline
- 2026-10-16 - CVE-2026-107758 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-107758
Vulnerability Analysis
The vulnerability is a stored XSS flaw that chains a server-side sanitization weakness with an unsafe client-side DOM operation. The Colibri plugin widened its comment allow-list to accept SVG elements along with arbitrary data-* attributes. Attackers can submit a comment containing an SVG element whose data-target attribute carries an HTML-encoded payload beginning with <. Because the allow-list treats data-* attributes as opaque strings, the payload passes KSES filtering and is written to the database. The injected markup remains dormant until a visitor loads any front-end page that enqueues colibri.js.
Root Cause
The root cause is a mismatch between server-side sanitization and client-side consumption of the stored data. The SVG KSES filter in extend-builder/filters/svg-kses.php permits SVG tags and arbitrary data-* attributes without validating their contents. On the client side, colibri.js reads data-target using jQuery.data(), which HTML-entity-decodes the attribute value. The decoded string is then passed directly into jQuery(), which parses any leading < as HTML and instantiates the resulting elements, firing embedded event handlers such as onload or onerror.
Attack Vector
An unauthenticated remote attacker submits a crafted comment containing an SVG tag with a data-target attribute holding an HTML-encoded script payload. The payload survives KSES filtering and is stored. When any visitor loads a page that enqueues colibri.js, the script reads the attribute via jQuery.data(), decodes it, and passes it to jQuery(), triggering script execution in the visitor's browser context. Refer to the Wordfence Vulnerability Report and the vulnerable source lines in the Colibri Page Builder JavaScript for implementation details.
Detection Methods for CVE-2026-107758
Indicators of Compromise
- Comments or stored content containing <svg elements with data-target attributes holding HTML-encoded tag sequences such as <img or <script.
- Unexpected outbound requests from visitor browsers to attacker-controlled domains originating from pages that load colibri.js.
- New or modified WordPress administrator accounts following comment submissions by unauthenticated users.
Detection Strategies
- Audit the wp_comments table for entries containing <svg, data-target=, or HTML entity-encoded angle brackets within the comment body.
- Monitor front-end page responses for SVG elements with suspicious data-* attributes that decode to executable markup.
- Review web server logs for comment submissions from unauthenticated sources targeting pages built with Colibri Page Builder.
Monitoring Recommendations
- Deploy a Content Security Policy (CSP) in report-only mode to surface inline script execution originating from stored comment payloads.
- Alert on any administrative session activity initiated from browser sessions that previously rendered untrusted comment content.
- Instrument endpoint telemetry to correlate browser-based XSS execution with downstream credential-use anomalies.
How to Mitigate CVE-2026-107758
Immediate Actions Required
- Update the Colibri Page Builder plugin to a version later than 1.0.390 as soon as the vendor publishes a fix.
- Disable the plugin on affected WordPress sites until a patched release is installed.
- Purge stored comments containing <svg elements with data-target attributes to prevent execution on patched systems.
Patch Information
At the time of publication, the vendor advisory indicates the vulnerability affects all versions up to and including 1.0.390. Administrators should monitor the Wordfence Vulnerability Report and the plugin repository for the official patched release.
Workarounds
- Disable comments site-wide or restrict comment submission to authenticated users with trusted roles until a patch is available.
- Deploy a web application firewall (WAF) rule to block POST requests containing <svg combined with data-target= in the comment parameter.
- Remove or dequeue colibri.js from front-end pages that do not require Colibri Page Builder functionality to break the exploitation chain.
# Example WAF ModSecurity rule to block the exploitation pattern
SecRule ARGS:comment "@rx (?i)<svg[^>]*data-[a-z-]+\s*=\s*['\"][^'\"]*(<|<)" \
"id:1072026,phase:2,deny,status:403,log,\
msg:'CVE-2026-107758 Colibri Page Builder stored XSS attempt'"
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

