CVE-2025-11361: CWE-918 Server-Side Request Forgery (SSRF) in wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns
The 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, 5.7.1 via the eb_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.
AI Analysis
Technical Summary
CVE-2025-11361 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns plugin for WordPress, affecting all versions up to and including 5.7.1. The vulnerability resides in the eb_save_ai_generated_image function, which improperly handles user input, allowing authenticated users with Author-level access or higher to induce the server to make HTTP requests to arbitrary locations. SSRF vulnerabilities enable attackers to bypass network restrictions by leveraging the vulnerable server as a proxy to access internal services that are otherwise inaccessible externally. In this case, the attacker can query internal endpoints, potentially extracting sensitive information or manipulating internal resources. The vulnerability does not require user interaction beyond authentication, and the attacker must have at least Author privileges, which are commonly assigned to content creators or editors in WordPress. The CVSS 3.1 base score is 6.4 (medium severity), reflecting the network attack vector, low attack complexity, and the requirement for privileges but no user interaction. The scope is changed (S:C) because the vulnerability can affect resources beyond the initially vulnerable component. No patches or exploits are currently publicly available, but the risk remains significant due to the potential for internal network reconnaissance and data exposure. The vulnerability is cataloged under CWE-918, which covers SSRF issues. Given the widespread use of WordPress and this plugin, the vulnerability poses a notable risk to websites that rely on these components for content management and page building.
Potential Impact
For European organizations, this SSRF vulnerability can lead to unauthorized internal network scanning and data exfiltration from internal services that are normally protected by network segmentation or firewalls. Attackers with Author-level access could leverage this flaw to gather sensitive information such as internal API endpoints, configuration data, or other protected resources, potentially facilitating further attacks like privilege escalation or lateral movement. This is particularly concerning for organizations hosting sensitive data or critical infrastructure on WordPress sites using this plugin. The vulnerability could also be exploited to modify internal service data if such services accept requests from the vulnerable server, leading to integrity breaches. Although the vulnerability does not directly cause denial of service, the indirect consequences of internal network compromise could be severe. European organizations with strict data protection regulations (e.g., GDPR) may face compliance risks if internal data is exposed or manipulated. The medium severity score suggests a moderate but actionable risk, especially in environments where multiple users have elevated WordPress privileges.
Mitigation Recommendations
1. Immediately restrict Author-level and higher privileges to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 2. Monitor and log outbound HTTP requests from WordPress servers to detect unusual or unauthorized internal network access patterns. 3. Implement network segmentation and firewall rules to limit the WordPress server's ability to reach sensitive internal services, reducing the attack surface for SSRF exploitation. 4. Disable or remove the Gutenberg Essential Blocks – Page Builder plugin if it is not essential to operations until a patch is released. 5. Regularly check for updates from the plugin vendor and apply patches promptly once available. 6. Conduct internal audits of WordPress user roles and permissions to ensure least privilege principles are enforced. 7. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SSRF attempts targeting the vulnerable function. 8. Educate site administrators and developers about the risks of SSRF and the importance of secure plugin management.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-11361: CWE-918 Server-Side Request Forgery (SSRF) in wpdevteam 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 Server-Side Request Forgery in all versions up to, and including, 5.7.1 via the eb_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.
AI-Powered Analysis
Technical Analysis
CVE-2025-11361 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns plugin for WordPress, affecting all versions up to and including 5.7.1. The vulnerability resides in the eb_save_ai_generated_image function, which improperly handles user input, allowing authenticated users with Author-level access or higher to induce the server to make HTTP requests to arbitrary locations. SSRF vulnerabilities enable attackers to bypass network restrictions by leveraging the vulnerable server as a proxy to access internal services that are otherwise inaccessible externally. In this case, the attacker can query internal endpoints, potentially extracting sensitive information or manipulating internal resources. The vulnerability does not require user interaction beyond authentication, and the attacker must have at least Author privileges, which are commonly assigned to content creators or editors in WordPress. The CVSS 3.1 base score is 6.4 (medium severity), reflecting the network attack vector, low attack complexity, and the requirement for privileges but no user interaction. The scope is changed (S:C) because the vulnerability can affect resources beyond the initially vulnerable component. No patches or exploits are currently publicly available, but the risk remains significant due to the potential for internal network reconnaissance and data exposure. The vulnerability is cataloged under CWE-918, which covers SSRF issues. Given the widespread use of WordPress and this plugin, the vulnerability poses a notable risk to websites that rely on these components for content management and page building.
Potential Impact
For European organizations, this SSRF vulnerability can lead to unauthorized internal network scanning and data exfiltration from internal services that are normally protected by network segmentation or firewalls. Attackers with Author-level access could leverage this flaw to gather sensitive information such as internal API endpoints, configuration data, or other protected resources, potentially facilitating further attacks like privilege escalation or lateral movement. This is particularly concerning for organizations hosting sensitive data or critical infrastructure on WordPress sites using this plugin. The vulnerability could also be exploited to modify internal service data if such services accept requests from the vulnerable server, leading to integrity breaches. Although the vulnerability does not directly cause denial of service, the indirect consequences of internal network compromise could be severe. European organizations with strict data protection regulations (e.g., GDPR) may face compliance risks if internal data is exposed or manipulated. The medium severity score suggests a moderate but actionable risk, especially in environments where multiple users have elevated WordPress privileges.
Mitigation Recommendations
1. Immediately restrict Author-level and higher privileges to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 2. Monitor and log outbound HTTP requests from WordPress servers to detect unusual or unauthorized internal network access patterns. 3. Implement network segmentation and firewall rules to limit the WordPress server's ability to reach sensitive internal services, reducing the attack surface for SSRF exploitation. 4. Disable or remove the Gutenberg Essential Blocks – Page Builder plugin if it is not essential to operations until a patch is released. 5. Regularly check for updates from the plugin vendor and apply patches promptly once available. 6. Conduct internal audits of WordPress user roles and permissions to ensure least privilege principles are enforced. 7. Employ Web Application Firewalls (WAFs) with rules designed to detect and block SSRF attempts targeting the vulnerable function. 8. Educate site administrators and developers about the risks of SSRF and the importance of secure plugin management.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-10-06T09:25:38.394Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68f319cceba81d1dad76b565
Added to database: 10/18/2025, 4:38:36 AM
Last enriched: 10/18/2025, 4:38:53 AM
Last updated: 10/19/2025, 9:22:08 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-11940: Uncontrolled Search Path in LibreWolf
HighCVE-2025-11939: Path Traversal in ChurchCRM
MediumCVE-2025-11938: Deserialization in ChurchCRM
MediumAI Chat Data Is History's Most Thorough Record of Enterprise Secrets. Secure It Wisely
MediumAI Agent Security: Whose Responsibility Is It?
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.