Colibri Page BuilderWordPress extension · Extendthemes
CVE-2025-32185
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 · uneditedImproper 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.329.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in the Colibri Page Builder plugin allows authenticated attackers to inject malicious JavaScript into pages built with the plugin. The vulnerability exists due to improper neutralization of user input during web page generation, allowing the stored payload to execute in victims' browsers when they access affected pages.
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
< 1.0.332CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Colibri Page Builder plugin is installedIn WordPress admin, go to Plugins > Installed Plugins. Look for 'Colibri Page Builder' by Extendthemes in the list.Affected if The plugin is listed in the installed plugins and the version shown is below 1.0.332
-
Verify the installed version numberClick on the plugin name or hover over it in the Plugins page to reveal the version number. Compare it against the affected range: versions prior to 1.0.332 are vulnerable.Affected if The displayed version number is less than 1.0.332
-
Confirm the plugin is active on the siteIn WordPress admin > Plugins, check that Colibri Page Builder shows as 'Active'. Only the active plugin can render malicious payloads in pages.Affected if The plugin status shows as Active and the version is below 1.0.332
-
Inspect pages built with the plugin for suspicious script tagsView the source HTML of pages created using the Page Builder. Look for unexpected <script> tags, script src attributes pointing to unknown domains, or inline event handlers (onload, onerror, onclick) containing encoded or obfuscated content.Affected if Unexpected JavaScript code is present in page HTML that was not intentionally added by site administrators
A site is affected if Colibri Page Builder version below 1.0.332 is installed and active, and pages built with it contain injected malicious scripts.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.332
Update to a patched version of Colibri Page Builder when available. Until then, implement output encoding/escaping on all user-supplied input and consider deploying a WAF rule to detect and block XSS attempts.
1.0.332 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Colibri Page Builder' in the plugin list
- Click 'Update now' if an update is available, or manually update to version 1.0.332 or later
- Verify the update completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Colibri Page Builder
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32185 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32185 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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