dbcve.org
Gutenberg Blocks With AiWordPress extension · Kadencewp

CVE-2023-6964

MEDIUM · 6.4 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 3.2.12 or later.
See remediation →
70/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
The Gutenberg Blocks by Kadence Blocks – Page Builder Features plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.26 via the 'kadence_import_get_new_connection_data' AJAX action. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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

The Kadence Blocks WordPress plugin contains an SSRF vulnerability in the 'kadence_import_get_new_connection_data' AJAX action, allowing authenticated users with contributor-level permissions to make arbitrary HTTP requests from the server. This can be exploited to probe internal services, bypass network restrictions, and access sensitive internal resources.

MitigationUpdate the Kadence Blocks plugin to version 3.1.27 or later. If immediate updating is not feasible, disable the plugin or restrict the vulnerable AJAX action access using a WAF or access 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.12

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify if Kadence Blocks plugin is installed
    Check the WordPress plugins directory for 'kadence-blocks' folder or look in wp-admin > Plugins for 'Kadence Gutenberg Blocks With Ai'
    Affected if The plugin appears in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number for Kadence Gutenberg Blocks With Ai, or inspect the plugin main file header for 'Version:' field
    Affected if Version is less than 3.2.12 (vulnerable)
  3. Verify contributor-level or higher user accounts exist
    In WordPress admin, go to Users > All Users and check for any users with role of Contributor, Author, Editor, or Administrator
    Affected if At least one user with contributor-level or higher access exists on the site
  4. Test AJAX action accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=kadence_import_get_new_connection_data and a valid nonce (can be obtained from page source if user is logged in as contributor)
    Affected if The AJAX action responds without returning a 403 or authentication error
  5. Check if the import/connection feature is enabled
    Look for any settings or options related to 'Import', 'Connection', or 'Kadence Import' in the plugin settings or check if the plugin provides any import functionality in the admin dashboard
    Affected if The import/connection feature exists and is accessible to contributor users

If Kadence Blocks version is below 3.2.12 AND the plugin is active AND contributor-level users exist on the site, the environment is affected by this SSRF vulnerability.

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.12 or later
Fixed in 3.2.12
Interim mitigation

Update the Kadence Blocks plugin to version 3.1.27 or later. If immediate updating is not feasible, disable the plugin or restrict the vulnerable AJAX action access using a WAF or access control.

Recommended fix High confidence

3.2.12

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Gutenberg Blocks With Ai' (or 'Kadence Blocks' with Ai extension)
  4. Click 'Update now' if an update is available, or manually upload version 3.2.12 or higher from the WordPress plugin repository
  5. After updating, verify the plugin version is 3.2.12 or later in Plugins > Installed Plugins

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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