Essential Blocks <= 5.7.2 - Missing Authorization To Authenticated (Author+) Information Disclosure
Strategic Overview
- Status
- Patched in 5.7.3
- Affected Version
<= 5.7.2- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-11369
At a glance
CVE-2025-11369 is a medium-severity Missing Authorization vulnerability in the Gutenberg Essential Blocks WordPress plugin, affecting versions <= 5.7.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 5.7.3; sites on affected versions should update now. Disclosed December 2025, reported by Dmitrii Ignatyev.
Vulnerability Overview
The Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns plugin for WordPress is vulnerable to unauthorized access of data due to a missing or incorrect capability checks on the get_instagram_access_token_callback, google_map_api_key_save_callback and get_siteinfo functions in all versions up to, and including, 5.7.2. This makes it possible for authenticated attackers, with Author-level access and above, to view API keys configured for the external services.
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.
CWE-862: Missing Authorization
Reaching this weakness in Gutenberg Essential Blocks <= 5.7.2 takes an account at Author level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Gutenberg Essential Blocks the fix is 5.7.3: builds <= 5.7.2 are affected, anything from 5.7.3 onward is not.
Remediation
Update to version 5.7.3, 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: Gutenberg Essential Blocks 5.7.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 5.4CVE-2023-51359: Essential Blocks… Incorrect Authorization Checks
CVE-2023-51359 - 4.3CVE-2025-26871: Essential Blocks for Gutenberg Missing Authorization
CVE-2025-26871 - 4.3CVE-2024-30467: Essential Blocks for Gutenberg Missing Authorization
CVE-2024-30467 - 4.3CVE-2023-47760: Essential Blocks for Gutenberg Missing Authorization
CVE-2023-47760
Other vulnerabilities in Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns
- 9.8CVE-2023-6623: Essential Blocks <= 4.4.2 Local File Inclusion
CVE-2023-6623 - 8.1CVE-2023-4402: Essential Blocks <= 4.2.0 PHP Object Injection
CVE-2023-4402 - 8.1CVE-2023-4386: Essential Blocks <= 4.2.0 PHP Object Injection
CVE-2023-4386 - 7.2CVE-2026-10586: Gutenberg Essential Blocks SSRF
CVE-2026-10586 - 6.4CVE-2026-10833: Gutenberg Essential Blocks - Page… Stored XSS
CVE-2026-10833 - 6.4CVE-2026-4658: Gutenberg Essential Blocks <= 6.0.4 Stored XSS
CVE-2026-4658 - 6.4CVE-2025-11361: Essential Blocks <= 5.7.1 Server-Side Request Forgery
CVE-2025-11361 - 6.4CVE-2025-11270: Gutenberg Essential Blocks Stored XSS
CVE-2025-11270
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C