Colibri Page Builder CVE-2025-9560
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as contributor-level user
-
DeliveryCraft malicious colibri_newsletter shortcode attributes
-
ExploitStore XSS payload in page content
-
ExecutionAdmin or visitor loads the page
-
ImpactExecute arbitrary script in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with contributor-level privileges or higher on a WordPress site running Colibri Page Builder version 1.0.334 or earlier, plus the ability to insert the colibri_newsletter shortcode into page content. The payload is delivered through unsanitized/unescaped user-supplied shortcode attributes and fires as Stored XSS when any user subsequently renders the affected page (no interaction needed from the attacker at execution time). Limiting factors: it is NOT remote-unauthenticated - an attacker must first obtain a contributor+ account, so single-admin or closed-registration sites have little exposure; the plugin must be installed and active at a vulnerable version; and impact is confined to script execution in the victim's browser context (no direct server compromise). |
| Impact | This is a moderate-severity, authenticated Stored XSS (CWE-79) with multiple signals pointing to limited real-world urgency rather than critical priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) indicates network reach and low complexity but requires privileges (PR:L) - specifically contributor-level WordPress access - which materially gates exploitation to users who already hold an account on the target site. The scope change (S:C) correctly reflects that the injected script executes in the browser of a different security context (any visitor/admin viewing the page), but confidentiality and integrity impact are only Low and availability is None. EPSS reinforces low near-term exploitation likelihood at 0.23% (13th percentile). There is no CISA KEV listing and no public exploit code identified in the provided data, so there is no evidence of active exploitation. There is no SSVC decision data supplied. No signals conflict here: a low EPSS, absent KEV, and an authenticated/privileged prerequisite all align to make this a routine patch-on-cycle item rather than an emergency - the main residual risk is on multi-author sites where untrusted contributors exist. |
| Exploit ScenarioDerived | A multi-author WordPress site allows contributor-level accounts (e.g., guest bloggers). A malicious or compromised contributor inserts a colibri_newsletter shortcode with crafted attributes containing a JavaScript payload into a draft page; because attributes are not sanitized or escaped, the script is stored and later executes in the browser of any administrator or visitor who views the page, enabling session/cookie theft or admin-action abuse. No public exploit code is identified at time of analysis, so exploitation currently requires an attacker to craft the payload manually. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in the WordPress plugin Colibri Page Builder (all versions through 1.0.334) allows an authenticated attacker holding a contributor-level account or higher to inject arbitrary JavaScript via unsanitized attributes of the colibri_newsletter shortcode, which then executes in the browser of any user who later views the affected page. The issue is scored CVSS 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), and exploitation is gated by real prerequisites: the plugin must be installed and active at a vulnerable version and the attacker must already control a contributor+ account capable of inserting shortcodes into content, so closed-registration and single-administrator sites have minimal exposure. No public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low at 0.23% (13th percentile), indicating limited real-world urgency rather than critical priority.
RemediationAI
The upstream fix is present as a code change in the WordPress plugin repository (changeset 3373432, modifying extend-builder/shortcodes/newsletter.php) rather than an explicitly stated tagged version in the available data - treat this as 'Upstream fix available (PR/commit); released patched version not independently confirmed' and verify the exact patched release number on the plugin's WordPress.org changelog/developers page (https://wordpress.org/plugins/colibri-page-builder/#developers) before considering the site remediated; any confirmed build newer than 1.0.334 that contains the changeset should be applied. If a verified patched release cannot be deployed immediately, the most effective compensating control is to deactivate Colibri Page Builder, which removes the shortcode sink entirely at the cost of losing the page-builder functionality and potentially altering the rendering of existing layouts, or to strip any existing colibri_newsletter shortcode occurrences from stored content. Additionally, restrict contributor-and-above roles to trusted users and prevent open self-registration or default role assignment to contributor, since the vulnerability is only reachable by an already-authenticated account at that privilege level. A WAF rule targeting the shortcode attributes or a Content-Security-Policy with a restrictive script-src directive can reduce the chance of payload execution but does not repair the underlying storage/output flaw and is bypassable, so these should be treated only as temporary hardening. Refer to the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/0ef1679f-44ec-448a-a77b-489ac9bfaa7a?source=cve) and the Trac changeset for verification.
Affected ProductsAI
The affected product is the Colibri Page Builder plugin for WordPress, in all versions up to and including 1.0.334, distributed through the WordPress.org plugin directory (see https://wordpress.org/plugins/colibri-page-builder/#developers). The vulnerable component is the plugin's colibri_newsletter shortcode, with the upstream code change landing in changeset 3373432 under trunk/extend-builder/shortcodes/newsletter.php (https://plugins.trac.wordpress.org/changeset/3373432/colibri-page-builder/trunk/extend-builder/shortcodes/newsletter.php). Sites are only exposed if the plugin is installed and active at a vulnerable version and permit contributor-level or higher accounts; the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/0ef1679f-44ec-448a-a77b-489ac9bfaa7a?source=cve is the primary third-party reference. No CPE strings were provided in the source data, so version-range matching must be done against the plugin's own version field rather than a CPE dictionary.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-79 improper neutralization of input during web page generation, manifesting specifically as Stored XSS inside the WordPress shortcode subsystem. Colibri Page Builder registers a shortcode named colibri_newsletter (implemented in extend-builder/shortcodes/newsletter.php) that accepts user-supplied attributes; those attribute values are neither sanitized on input nor escaped on output, so attacker-controlled markup is persisted as part of the post/page content and re-emitted verbatim whenever the shortcode is rendered. Because WordPress grants contributor-level users the ability to create and edit their own posts and pages - including inserting shortcodes - such an account is sufficient to plant the payload, and the script fires with no further interaction required from the attacker once a victim (author, editor, administrator, or any front-end visitor) loads the affected page. The CVSS vector's Scope:Changed (S:C) reflects that code executes in the victim's browser context, transcending the vulnerable plugin component, though Confidentiality and Integrity impacts remain Low and no server-side compromise is achieved. Relevant metadata: the WordPress plugin directory entry and its Trac changeset (3373432) touching the newsletter shortcode file document the code path; no CPE identifiers were supplied with the input data.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Contributor authentication is required (PR:L), stored payload needs no victim interaction to trigger (UI:N), and execution in another browser context is a scope change (S:C) with Low C/I and no availability impact.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The Colibri Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's colibri_newsletter shortcode in all versions up to, and including, 1.0.334 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB