Colibri Page BuilderWordPress extension · Extendthemes

CVE-2025-59593

MEDIUM · 5.9 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 1.0.334 or later.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Extend Themes Colibri Page Builder colibri-page-builder allows Stored XSS.This issue affects Colibri Page Builder: from n/a through < 1.0.334.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored XSS vulnerability in Extend Themes Colibri Page Builder plugin allows authenticated attackers to inject malicious JavaScript through plugin inputs that get stored and executed when other users view affected pages. The vulnerability affects versions prior to 1.0.334.

MitigationUpdate Colibri Page Builder to version 1.0.334 or later to obtain the security patch. Investigate the site for signs of exploitation and sanitize existing content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Colibri Page BuilderWordPress extension
Affected:< 1.0.334

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Colibri Page Builder plugin installation
    Check the WordPress plugins directory at wp-content/plugins/colibri-page-builder or view the installed plugins list in the WordPress admin under Plugins
    Affected if Plugin files are found in the plugins directory
  2. Determine the installed plugin version
    Open the main plugin file (usually colibri-page-builder.php) and locate the version constant defined in the plugin header, or check the plugin details in WordPress admin plugins list
    Affected if Version shown is less than 1.0.334
  3. Verify the plugin is active
    In WordPress admin, check the Plugins list to confirm Colibri Page Builder shows as Active
    Affected if Plugin is active on the site
  4. Inspect plugin-stored content for suspicious scripts
    Review page content created with the Page Builder in the WordPress editor; examine raw database entries in wp_posts or related tables for unexpected script tags, event handlers, or encoded JavaScript
    Affected if Unexpected JavaScript tags or event handlers are present in plugin-generated content

User is affected if Colibri Page Builder is installed, active, and the installed version is prior to 1.0.334.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.334 or later
Fixed in 1.0.334
Interim mitigation

Update Colibri Page Builder to version 1.0.334 or later to obtain the security patch. Investigate the site for signs of exploitation and sanitize existing content.

Recommended fix Moderate confidence

Colibri Page Builder 1.0.334 or later

  1. Back up your WordPress site and database before performing any updates
  2. Navigate to your WordPress dashboard and go to Plugins > Installed Plugins
  3. Locate Colibri Page Builder in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.0.334 or later of Colibri Page Builder
  5. Verify the plugin has been updated to version 1.0.334 or newer
  6. Test the affected functionality (forms, user inputs, content rendering) to confirm the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Colibri Page Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59593 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data