dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-7465

HIGH · 8.8 CVSS v3.1 Published 2026-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Spectra Gutenberg Blocks – Website Builder for the Block Editor plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.19.25. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. Exploitation requires a two-block payload embedded in post content: the first block registers a fake uagb/-prefixed block type with an attacker-specified render_callback, and the second block of the same fake type triggers invocation of that callback via call_user_func() during sequential block rendering in the same page request.

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 confidence

Authenticated RCE in Spectra Gutenberg Blocks plugin where Contributor+ users can register a fake uagb/-prefixed block type with attacker-controlled render_callback, then trigger execution via call_user_func() during sequential block rendering.

MitigationUpdate Spectra plugin to version beyond 2.19.25 when available, or disable/remove the plugin until patched. This is a critical RCE vulnerability requiring immediate attention.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Spectra Gutenberg Blocks plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Spectra Gutenberg Blocks' (or 'Ultimate Addons for Gutenberg'). Note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' comment, typically in /wp-content/plugins/ultimate-addons-for-gutenberg/ or similar path.
    Affected if The installed version is 2.19.25 or lower.
  2. Identify Contributor-level user accounts
    In WordPress admin, go to Users > All Users. Review the 'Role' column for any users assigned the Contributor role. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'contributor'.
    Affected if At least one user account with Contributor role exists in the WordPress installation.
  3. Verify Gutenberg block editor is active
    Confirm the WordPress block editor (Gutenberg) is enabled. Check if the plugin's block functionality is accessible by creating a new post/page and verifying that Spectra/uagb blocks appear in the block inserter.
    Affected if The Gutenberg block editor is active and Spectra blocks are available for use by Contributors.
  4. Inspect for suspicious uagb-prefixed custom blocks
    Review the WordPress database wp_posts table for post_content containing block markup with 'uagb/' prefix that may indicate malicious block registration, particularly look for blocks with render_callback attributes in the block JSON.
    Affected if Custom uagb-prefixed blocks with render_callback parameters are found in post content.

A user is affected if their Spectra Gutenberg Blocks plugin version is 2.19.25 or lower AND Contributor-level users exist with access to the Gutenberg block editor.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Spectra plugin to version beyond 2.19.25 when available, or disable/remove the plugin until patched. This is a critical RCE vulnerability requiring immediate attention.

Recommended fix Moderate confidence

Version 2.20.0 or later

  1. Check your currently installed version of the Spectra Gutenberg Blocks (Ultimate Addons for Gutenberg) plugin
  2. Navigate to WordPress admin > Plugins and locate the Spectra plugin to verify the current version number
  3. Upgrade the plugin to version 2.20.0 or later via WordPress admin > Plugins > Add New > Upload, or via the plugin's update mechanism
  4. After upgrading, verify the new version is active and the site functionality remains intact
  5. Review user roles and permissions to ensure only trusted users have Contributor-level or higher access
Caveat Standard minor version upgrade; verify custom block templates still render correctly after update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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 locally
dbcve dependency scanner

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