Free Gutenberg BlocksWordPress extension · Gutengeek
CVE-2024-9073
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 GutenGeek Free Gutenberg Blocks for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 1.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.
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 GutenGeek Free Gutenberg Blocks plugin fails to sanitize SVG file uploads, allowing authenticated users with Author-level access or higher to upload malicious SVG files containing embedded JavaScript. When users access these uploaded SVG files, the embedded scripts execute in their browsers, leading to stored XSS.
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
Free Gutenberg BlocksWordPress extension
<= 1.1.3CVSS 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.
-
Verify plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and check the version of 'Gutengeek Free Gutenberg Blocks' plugin. Compare against <= 1.1.3Affected if Plugin version is 1.1.3 or lower and the plugin is active
-
Confirm SVG upload capability is availableCheck if the plugin's block editor components that allow media uploads are accessible. Test by attempting to add an image block or using the plugin's file upload feature if it exists in the editorAffected if Authenticated users with Author role or higher can access media upload functionality in the editor
-
Identify uploaded SVG files on the serverSearch the wp-content/uploads directory for .svg files: find /path/to/wp-content/uploads -name "*.svg" -type f. Check file contents for suspicious patterns like <script> tags, onload, onerror, or javascript: attributesAffected if SVG files exist in uploads and contain embedded JavaScript or event handlers (onload, onerror, onclick, etc.)
-
Review user roles with upload accessIn WordPress admin, go to Users > All Users and identify accounts with Author role or higher. These users have the capability to upload filesAffected if There are users with Author-level or higher access who could have uploaded malicious SVGs
-
Check web server access logs for SVG file requestsReview web server access logs (Apache/Nginx) for requests to uploaded SVG files, especially from admin pages or user profile areas. Look for GET requests to paths like /wp-content/uploads/*/*.svgAffected if SVG files from the uploads directory are being accessed, which could indicate exploitation in progress
Environment is affected if Gutengeek Free Gutenberg Blocks version 1.1.3 or lower is active and users with Author role or higher can upload SVG files, or if uploaded SVG files with embedded scripts already exist on the server.
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.
From vendor dataUpdate the plugin to the latest patched version. If no patch is available, disable SVG uploads entirely or implement server-side sanitization to strip script tags and event handlers from SVG files.
Fix this in Free Gutenberg Blocks
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9073 — 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-9073 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