Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11369: CWE-862 Missing Authorization in wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns

0
Medium
VulnerabilityCVE-2025-11369cvecve-2025-11369cwe-862
Published: Wed Dec 17 2025 (12/17/2025, 01:48:52 UTC)
Source: CVE Database V5
Vendor/Project: wpdevteam
Product: Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns

Description

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.

AI-Powered Analysis

AILast updated: 12/24/2025, 04:47:52 UTC

Technical Analysis

CVE-2025-11369 is a missing authorization vulnerability (CWE-862) found in the Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns WordPress plugin, versions up to and including 5.7.2. The vulnerability stems from inadequate capability checks on three key functions: get_instagram_access_token_callback, google_map_api_key_save_callback, and get_siteinfo. These functions handle sensitive operations related to retrieving API keys for Instagram and Google Maps services, as well as site information. Because the plugin fails to properly verify whether the requesting user has sufficient privileges, any authenticated user with Author-level permissions or higher can invoke these functions to access API keys configured within the plugin. This unauthorized access could allow attackers to misuse these keys to interact with external services, potentially leading to data exfiltration or service abuse. The vulnerability is exploitable remotely without user interaction, and the attack vector is network-based. However, exploitation requires the attacker to have at least Author-level credentials on the WordPress site, which limits the attack surface to insiders or compromised accounts. The CVSS 3.1 score of 4.3 reflects a low to medium impact primarily on confidentiality, with no impact on integrity or availability. No public exploits or active exploitation have been reported to date. The absence of patches at the time of disclosure necessitates immediate attention from site administrators to apply any forthcoming updates or implement compensating controls.

Potential Impact

For European organizations, this vulnerability poses a risk of unauthorized disclosure of API keys used for Instagram and Google Maps integrations on WordPress sites employing the affected plugin. Exposure of these keys can lead to unauthorized access or abuse of external services, potentially resulting in data leakage, reputational damage, or financial loss if attackers leverage the keys for malicious activities such as data scraping, fraudulent API usage, or service disruption. Organizations with multiple WordPress sites or those relying heavily on third-party integrations are particularly at risk. Since the vulnerability requires Author-level access, the threat is elevated in environments where user account management is lax or where insider threats exist. The impact is more pronounced for public-facing websites that integrate social media or mapping services, common in sectors like media, retail, tourism, and public administration across Europe. Although the vulnerability does not directly compromise site integrity or availability, the indirect consequences of API key misuse can be significant, especially if attackers pivot to further attacks using stolen credentials.

Mitigation Recommendations

European organizations should immediately audit user roles and permissions on WordPress sites using the Gutenberg Essential Blocks plugin to ensure that only trusted users have Author-level or higher access. Implement strict access controls and monitor for unusual account activity. Until an official patch is released, consider disabling or removing the plugin if feasible, or restrict access to the affected functions through custom code or security plugins that enforce capability checks. Employ web application firewalls (WAFs) to detect and block suspicious requests targeting the vulnerable functions. Rotate any exposed API keys for Instagram and Google Maps to invalidate potentially compromised credentials. Regularly update WordPress core, plugins, and themes to incorporate security fixes promptly. Additionally, conduct security awareness training for site administrators and content authors to reduce the risk of credential compromise. Monitor security advisories from the plugin vendor and WordPress security teams for patch releases and further guidance.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-06T13:48:08.856Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69421096473cb759e1e64bfb

Added to database: 12/17/2025, 2:08:22 AM

Last enriched: 12/24/2025, 4:47:52 AM

Last updated: 2/7/2026, 2:32:31 PM

Views: 79

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats