The Colibri Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the…

Why it is Yellow

• CVSS 7.2 high
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/colibri-page-builder/trunk/extend-builder/assets/static/colibri.js#L205
• https://plugins.trac.wordpress.org/browser/colibri-page-builder/trunk/extend-builder/assets/static/colibri.js#L57
• https://plugins.trac.wordpress.org/browser/colibri-page-builder/trunk/extend-builder/filters/svg-kses.php#L4
• https://plugins.trac.wordpress.org/browser/colibri-page-builder/trunk/extend-builder/filters/svg-kses.php#L68
• https://plugins.trac.wordpress.org/browser/colibri-page-builder/trunk/extend-builder/filters/svg-kses.php#L82
• https://www.wordfence.com/threat-intel/vulnerabilities/id/ccae5cbd-cfe6-48b3-8bcd-0b08ceb94680?source=cve

Original description

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.