dbcve.org
ComboblocksWordPress extension · Pickplugins

CVE-2024-6346

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 2.2.86 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 Gutenberg Blocks, Page Builder – ComboBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the redirectURL parameter of the Date Countdown widget, in all versions up to, and including, 2.2.85 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.

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 ComboBlocks WordPress plugin contains a stored XSS vulnerability in its Date Countdown widget. The redirectURL parameter lacks proper input sanitization and output escaping, allowing authenticated contributors and above to inject arbitrary JavaScript that executes when users access affected pages.

MitigationUpdate ComboBlocks to version 2.2.86 or later which contains the security fix; alternatively, remove or restrict contributor-level access until patched.

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
ComboblocksWordPress extension
Affected:< 2.2.86

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. Confirm ComboBlocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'ComboBlocks' (formerly 'Pickplugins Comboblocks'). Note the installed version number displayed there.
    Affected if Plugin is installed and version is below 2.2.86
  2. Identify Date Countdown widget usage
    Navigate to the Pages or Posts section in WordPress admin. Review any pages or posts that use the ComboBlocks Date Countdown widget, or check your widget areas if using widget blocks.
    Affected if Date Countdown widget is actively used on any published page, post, or widget area
  3. Inspect redirectURL configuration
    Edit each page/post containing the Date Countdown widget. Open the widget settings and locate the 'redirectURL' or redirect URL field. Check if the value contains script tags, javascript:, or other unexpected characters.
    Affected if The redirectURL field contains unescaped HTML/JavaScript such as <script>, javascript:, or onerror= attributes
  4. Verify user role permissions
    Check WordPress Users > All Users to see which accounts have Contributor role or higher. Contributors can edit their own posts and may have access to the Date Countdown widget.
    Affected if Any user with Contributor-level or higher access has created or modified content using the Date Countdown widget

You are affected if ComboBlocks plugin version is below 2.2.86 AND the Date Countdown widget with a potentially malicious redirectURL is published on your site.

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 2.2.86 or later
Fixed in 2.2.86
Interim mitigation

Update ComboBlocks to version 2.2.86 or later which contains the security fix; alternatively, remove or restrict contributor-level access until patched.

Recommended fix High confidence

2.2.86

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the ComboBlocks (Gutenberg Blocks, Page Builder) plugin
  4. Click 'Update now' if an update is available, or manually update to version 2.2.86
  5. Verify the plugin updated successfully to version 2.2.86 or higher
  6. Clear any caching if applicable
Caveat Security patch with minimal risk; standard minor version update

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

Fix this in Comboblocks Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6346 — 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-2024-6346 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