dbcve.org
Gutenberg Blocks With AiWordPress extension · Kadencewp

CVE-2024-23500

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to 3.2.20 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in StellarWP Gutenberg Blocks by Kadence Blocks kadence-blocks.This issue affects Gutenberg Blocks by Kadence Blocks: from n/a through <= 3.2.19.

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

Server-Side Request Forgery (SSRF) vulnerability in Kadence Blocks WordPress plugin allows attackers to make the server perform unintended requests to internal or external resources due to insufficient URL validation in the Gutenberg blocks functionality.

MitigationUpdate Kadence Blocks plugin to version 3.2.20 or later. If immediate update is not possible, restrict outbound network access from the web server and implement URL allowlisting as a compensating control.

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
Gutenberg Blocks With AiWordPress extension
Affected:< 3.2.20

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Kadence Blocks plugin is installed
    Check your WordPress installation for the Kadence Blocks plugin. This can be done via WordPress admin dashboard under Plugins, or by checking the /wp-content/plugins/kadence-blocks directory exists on the server.
    Affected if The Kadence Blocks plugin is present in the WordPress installation
  2. Identify the installed Kadence Blocks version
    Locate the plugin version number. In WordPress admin, go to Plugins > Installed Plugins and find the version listed under Kadence Blocks. Alternatively, check the main plugin file header in kadence-blocks/class-kadence-blocks.php for the 'Version' comment, or use 'wp plugin list' via wp-cli.
    Affected if The version number is lower than 3.2.20
  3. Confirm Gutenberg block editor is active
    Verify that the block editor (Gutenberg) is enabled on the site. This can be checked in WordPress admin under Settings > Writing > Use the block editor, or by attempting to edit a post using the block editor interface.
    Affected if The block editor is active and Kadence custom blocks are available for use

A user is affected if Kadence Blocks plugin is installed with a version lower than 3.2.20 and the Gutenberg block editor with Kadence blocks is in use.

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

Update Kadence Blocks plugin to version 3.2.20 or later. If immediate update is not possible, restrict outbound network access from the web server and implement URL allowlisting as a compensating control.

Recommended fix High confidence

Version 3.2.20 or later of Gutenberg Blocks With Ai (Kadence Blocks)

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Gutenberg Blocks With Ai' (or 'Kadence Blocks') in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 3.2.20
  5. Verify the plugin version shows 3.2.20 or higher after updating
  6. Test that the site's frontend and editor functionality work correctly

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

Fix this in Gutenberg Blocks With Ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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