---
id: "CVE-2026-107758"
kind: "vulnerability"
aliases: ["CVE-2026-107758"]
title: "Colibri Page Builder WordPress plugin: stored XSS via comment parameter"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["colibri-page-builder", "package", "self-hosted", "wordpress", "wordpress-plugin"]
not_affected_if: ["plugin-not-installed"]
published_at: "2026-10-16T04:18:24+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:29:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107758", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# Colibri Page Builder WordPress plugin: stored XSS via comment parameter

The Colibri Page Builder plugin for WordPress stores attacker-supplied SVG markup through its 'comment' parameter without adequate sanitization, and the front-end script later renders it as HTML. An unauthenticated attacker can inject JavaScript that runs in the browser of any user who opens an affected page, including administrators.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Colibri Page Builder plugin version in the WordPress admin Plugins screen or `wp plugin get colibri-page-builder --field=version`
- Confirm whether the plugin is active with `wp plugin list --status=active`

## Fix

- Update the Colibri Page Builder plugin to a version later than `1.0.390`, as published by the plugin vendor
- Unknown whether a patched version number is confirmed in the sources

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-107758

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_