CVE-2024-9234
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 GutenKit – Page Builder Blocks, Patterns, and Templates for Gutenberg Block Editor plugin for WordPress is vulnerable to arbitrary file uploads due to a missing capability check on the install_and_activate_plugin_from_external() function (install-active-plugin REST API endpoint) in all versions up to, and including, 2.1.0. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins, or utilize the functionality to upload arbitrary files spoofed like plugins.
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 GutenKit WordPress plugin has a critical unauthenticated privilege escalation vulnerability in its REST API endpoint (install-active-plugin). The install_and_activate_plugin_from_external() function lacks capability checks, allowing any unauthenticated attacker to install and activate arbitrary plugins from external sources, achieving full site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm GutenKit plugin is installedInspect your WordPress plugins directory or access the Plugins page in the WordPress admin dashboard to locate the GutenKit plugin entryAffected if The GutenKit plugin appears in your installed plugins list
-
Identify the installed version numberOn the Plugins page in WordPress admin, click on the plugin name to view details, or inspect the main plugin file (usually gutenkit.php) to find the version declared in the plugin headerAffected if The version displayed is below 2.1.1 or no version number is visible (older or unpatched release)
-
Verify the vulnerable REST API endpoint existsSend a GET request to /wp-json/gutenkit/v1/install-active-plugin using a tool like curl or browser developer tools; check if the endpoint returns any response (even an error or 401) rather than a 404Affected if The endpoint responds with any HTTP status other than 404, indicating the vulnerable route is registered and accessible
-
Confirm the plugin is activeCheck the Plugins > Installed Plugins page in WordPress admin; the GutenKit plugin must show as 'Active' for the vulnerability to be exploitableAffected if GutenKit is currently activated on the site
Your environment is affected if GutenKit is installed, active, and the installed version is any version prior to 2.1.1, regardless of whether the REST API endpoint returns an error or success response.
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 · scopedUpdate to version 2.1.1 or later immediately; if unavailable, disable or remove the plugin entirely until a patch is released, and audit the site for unauthorized plugins or backdoors.
Latest version beyond 2.1.0 (check wordpress.org for current release)
- Upgrade the GutenKit plugin to the latest available version from the official WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9234 — 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-9234 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