dbcve.org
Colibri Page BuilderWordPress extension · Extendthemes

CVE-2023-6988

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-11
Fix available
A fix is available. Upgrade to after 1.0.239 or later.
See remediation →
58/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
The Colibri Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's extend_builder_render_js shortcode in all versions up to, and including, 1.0.239 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 · high confidence

The Colibri Page Builder WordPress plugin before version 1.0.240 contains a stored XSS vulnerability in its extend_builder_render_js shortcode. Authenticated users with contributor-level permissions can inject arbitrary JavaScript via unsanitized shortcode attributes, which executes when other users view the affected pages.

MitigationUpdate the Colibri Page Builder plugin to version 1.0.240 or later. Until updated, restrict contributor-level user permissions and review existing pages for malicious shortcode injections.

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.239

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
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 checks

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

  1. Verify Colibri Page Builder plugin version
    Go to WordPress admin > Plugins > Installed Plugins, locate 'Colibri Page Builder' by Extendthemes, and note the version number shown
    Affected if The version listed is 1.0.239 or lower
  2. Identify use of the vulnerable shortcode
    Search your WordPress database or content for the shortcode tag 'extend_builder_render_js' - this can be done via plugin search tools, phpMyAdmin search, or WP-CLI command: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%extend_builder_render_js%'" (adjusting table prefix as needed)
    Affected if Any pages, posts, or custom post types contain the extend_builder_render_js shortcode
  3. Inspect shortcode attributes for injection attempts
    Examine pages containing the shortcode and review the attribute values, looking for unsanitized or suspicious-looking JavaScript code patterns (such as event handlers like onmouseover, onerror, or javascript: URLs)
    Affected if The shortcode attributes contain executable JavaScript or HTML that was not intentionally added by an administrator
  4. Review contributor-level user accounts
    In WordPress admin, go to Users > All Users and identify any accounts with the 'Contributor' role or higher (Author, Editor, Administrator)
    Affected if There are contributor-level or higher users who could potentially exploit this vulnerability

You are affected if the Colibri Page Builder plugin version is 1.0.239 or lower AND the extend_builder_render_js shortcode is present in your content with untrusted attribute values.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.239
Interim mitigation

Update the Colibri Page Builder plugin to version 1.0.240 or later. Until updated, restrict contributor-level user permissions and review existing pages for malicious shortcode injections.

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-2023-6988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-6988 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