CVE-2026-107758: Colibri Page Builder <= 1.0.390 - Unauthenticated Stored Cross-Site Scripting via Comments
The Colibri Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.0.390 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload survives storage because the widened comment allow-list permits SVG elements with arbitrary data- attributes; execution occurs because colibri.js, enqueued globally on every front-end page, reads the stored data-target value via jQuery.data() — which HTML-entity-decodes it — and passes the resulting string directly into jQuery(), which parses a leading '<' as HTML and fires the embedded event handler.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue, and what user interaction is required?
An unauthenticated attacker can submit a crafted comment parameter; no attacker authentication or victim interaction beyond visiting a page containing the stored payload is required. The script executes when a user accesses the injected page.
Are ordinary front-end pages affected, or only specific builder pages?
The vulnerable colibri.js script is enqueued globally on every front-end page. A stored payload can therefore execute whenever a user visits an injected front-end page.
What makes the stored payload execute?
The widened comment allow-list permits SVG elements with arbitrary data-* attributes, allowing the payload to survive storage. colibri.js reads the stored data-target value through jQuery.data(), which entity-decodes it, then passes it to jQuery() for HTML parsing and event-handler execution.