Spectra Gutenberg Blocks <= 2.19.25 - Authenticated (Contributor+) Remote Code Execution via Arbitrary PHP Function Call via Block Attributes
Strategic Overview
- Status
- Patched in 2.19.26
- Affected Plugin
- Spectra Legacy – Gutenberg Blocks
- Affected Version
<= 2.19.25- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-7465
At a glance
CVE-2026-7465 is a high-severity Improper Privilege Management vulnerability in the Spectra Legacy WordPress plugin, affecting versions <= 2.19.25. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.19.26; sites on affected versions should update now. Disclosed May 2026, reported by kai63001.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Spectra Legacy <= 2.19.25 carries this weakness at call_user_func(), and reaching it takes an account at Contributor level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Spectra Legacy the fix is 2.19.26: builds <= 2.19.25 are affected, anything from 2.19.26 onward is not.
Remediation
Update to version 2.19.26, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Spectra Legacy 2.19.26 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Spectra Legacy – Gutenberg Blocks
- 8.5CVE-2023-36679: Spectra <= 2.6.6 SSRF in import_wpforms
CVE-2023-36679 - 6.5CVE-2023-23735: Spectra HTML Injection in Emails
CVE-2023-23735 - 6.4CVE-2026-12900: Spectra Gutenberg Blocks <= 2.19.28 Stored XSS
CVE-2026-12900 - 6.4CVE-2025-11162: Spectra <= 2.19.14 Stored Cross-Site Scripting
CVE-2025-11162 - 6.4CVE-2025-1784: Spectra – WordPress Gutenberg Blocks Stored XSS
CVE-2025-1784 - 6.4CVE-2024-10484: Spectra – WordPress Gutenberg Blocks Stored XSS
CVE-2024-10484 - 6.4CVE-2024-7590: Spectra – WordPress Gutenberg Blocks Stored XSS
CVE-2024-7590 - 6.4CVE-2024-4366: Spectra – WordPress Gutenberg Blocks Stored XSS
CVE-2024-4366
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C