Gutenberg Blocks With AiWordPress extension · Kadencewp
CVE-2024-2273
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 · uneditedThe Gutenberg Blocks by Kadence Blocks – Page Builder Features plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in all versions up to, and including, 3.2.34 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, 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 confidenceThe Kadence Blocks WordPress plugin versions up to 3.2.34 contain a stored Cross-Site Scripting vulnerability. Authenticated attackers with contributor-level permissions or higher can inject arbitrary JavaScript through insufficiently sanitized plugin parameters. The malicious payload persists in page content and executes whenever users access those 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
Gutenberg Blocks With AiWordPress extension
< 3.2.35CVSS 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.
-
Identify Kadence Blocks plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find 'Kadence Blocks - Gutenberg Blocks with AI Kit', and note the version number displayedAffected if Version is 3.2.34 or lower (versions below 3.2.35 are vulnerable)
-
Confirm plugin is activeCheck that the Kadence Blocks plugin is currently activated on the WordPress siteAffected if Plugin is active and version is below 3.2.35
-
Review content for suspicious script injectionsInspect page/post content that uses Kadence Blocks (specifically row, advanced btn, or info box blocks) for unexpected script tags, event handlers, or javascript: URIs in parametersAffected if Malicious JavaScript payloads are present in stored page content
-
Audit contributor-level or higher user accountsGo to Users > All Users and identify accounts with Contributor, Author, Editor, or Administrator rolesAffected if Untrusted or compromised accounts with contributor-level or higher permissions exist on the site
You are affected if the Kadence Blocks plugin version is below 3.2.35 and untrusted users with contributor-level or higher access exist on the site, or if suspicious script injections are found in pages using Kadence Blocks.
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 · scoped3.2.35
Update Kadence Blocks plugin to version 3.2.35 or later which includes proper input sanitization and output escaping to neutralize the XSS vector.
Version 3.2.35 or later of Gutenberg Blocks by Kadence Blocks – Page Builder Features plugin
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Gutenberg Blocks by Kadence Blocks – Page Builder Features' plugin
- If automatic updates are enabled, the plugin should automatically update to version 3.2.35 or later
- If automatic updates are not enabled, click 'Update Now' on the plugin to update to the latest version (3.2.35 or higher)
- After updating, verify the installed version is 3.2.35 or higher by checking the Plugins page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gutenberg Blocks With Ai
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2273 — 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-2024-2273 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