CVE-2026-10586
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 Essential Blocks – Page Builder for Gutenberg Blocks & Patterns plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.1.3 via the `save_ai_generated_image()` function. This makes it possible for authenticated attackers, with Author-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 · high confidenceThe Gutenberg Essential Blocks WordPress plugin contains an SSRF vulnerability in the save_ai_generated_image() function affecting versions up to 6.1.3. Authenticated users with Author-level permissions or higher can abuse this to make arbitrary HTTP requests from the server, potentially reaching internal network resources or exfiltrating data.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Gutenberg Essential Blocks plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find 'Gutenberg Essential Blocks' to see the installed version number, or inspect the plugin's main PHP file (e.g., /wp-content/plugins/essential-blocks/gutenberg-essential-blocks.php) for the Version header commentAffected if The displayed version is 6.1.3 or lower (any version up to and including 6.1.3)
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Instored Plugins and verify that 'Gutenberg Essential Blocks' shows as 'Active'Affected if The plugin is active and the version is 6.1.3 or lower
-
Verify the vulnerable function existsInspect the plugin files (e.g., search for 'save_ai_generated_image' in the plugin directory under /wp-content/plugins/essential-blocks/) to confirm the function is present in the codebaseAffected if The function save_ai_generated_image() exists in the plugin code and the version is 6.1.3 or lower
-
Check for exposed AJAX endpointLook for AJAX action hooks tied to save_ai_generated_image (typically in the format 'wp_ajax_save_ai_generated_image' or 'wp_ajax_nopriv_save_ai_generated_image') in the plugin's PHP filesAffected if The AJAX action is registered without capability checks beyond Author-level access, and the version is 6.1.3 or lower
The environment is affected if Gutenberg Essential Blocks plugin is active at version 6.1.3 or lower, as this version range contains the vulnerable save_ai_generated_image() function exploitable by authenticated Author-level users.
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 a version beyond 6.1.3 once available. Until then, restrict the 'Author' role capability or disable the AI image generation feature if possible.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10586 — 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-2026-10586 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