CVE-2026-6394: CWE-918 Server-Side Request Forgery (SSRF) in wpdive Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to and including 1.1.1. This is due to the import_demo() function accepting a user-supplied URL in the demo_json_file POST parameter and passing it directly to wp_remote_get() without any URL validation or restriction against internal or private network destinations. The nexa_blocks_nonce required for the AJAX action is publicly exposed in the HTML source of any frontend page where the plugin is active via wp_localize_script on the enqueue_block_assets hook, effectively making the nonce available to all visitors and bypassing any intended authentication barrier. This makes it possible for unauthenticated attackers to make server-side HTTP requests to arbitrary internal or external destinations, potentially exposing internal services, cloud metadata endpoints such as the AWS instance metadata service, localhost services, and other resources not intended to be publicly accessible. A secondary SSRF vector also exists whereby image URLs extracted from the attacker-controlled JSON response are subsequently fetched via a second wp_remote_get() call, allowing chained exploitation through a crafted JSON payload.
AI Analysis
Technical Summary
The Nexa Blocks WordPress plugin contains an SSRF vulnerability (CWE-918) due to the import_demo() function accepting unvalidated user input in the demo_json_file POST parameter and passing it directly to wp_remote_get(). The required AJAX nonce is publicly exposed in frontend HTML, allowing unauthenticated attackers to exploit this SSRF to access internal or private network resources, including cloud metadata services like AWS instance metadata. Additionally, a secondary SSRF vector exists through image URLs fetched from attacker-controlled JSON responses, enabling chained exploitation. The vulnerability affects versions up to 1.1.1 and has a CVSS 3.1 base score of 5.4, indicating medium severity. The service is cloud-hosted, and a patch is available.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to make server-side HTTP requests to arbitrary internal or external destinations. This may expose sensitive internal services, cloud metadata endpoints (e.g., AWS instance metadata), localhost services, and other resources not intended to be publicly accessible. The secondary SSRF vector increases the attack surface by allowing chained requests through crafted JSON payloads. The impact includes potential information disclosure and reconnaissance within internal networks or cloud environments.
Mitigation Recommendations
A patch is available for this vulnerability. Since the affected product is a cloud-hosted service, the vendor manages remediation server-side. Users should verify with the vendor advisory that the patch has been applied. No additional action is required if the vendor confirms mitigation. If not confirmed, users should avoid using affected plugin versions and monitor vendor communications for updates.
CVE-2026-6394: CWE-918 Server-Side Request Forgery (SSRF) in wpdive Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
Description
The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to and including 1.1.1. This is due to the import_demo() function accepting a user-supplied URL in the demo_json_file POST parameter and passing it directly to wp_remote_get() without any URL validation or restriction against internal or private network destinations. The nexa_blocks_nonce required for the AJAX action is publicly exposed in the HTML source of any frontend page where the plugin is active via wp_localize_script on the enqueue_block_assets hook, effectively making the nonce available to all visitors and bypassing any intended authentication barrier. This makes it possible for unauthenticated attackers to make server-side HTTP requests to arbitrary internal or external destinations, potentially exposing internal services, cloud metadata endpoints such as the AWS instance metadata service, localhost services, and other resources not intended to be publicly accessible. A secondary SSRF vector also exists whereby image URLs extracted from the attacker-controlled JSON response are subsequently fetched via a second wp_remote_get() call, allowing chained exploitation through a crafted JSON payload.
CVSS v3.1
Score 5.4medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Nexa Blocks WordPress plugin contains an SSRF vulnerability (CWE-918) due to the import_demo() function accepting unvalidated user input in the demo_json_file POST parameter and passing it directly to wp_remote_get(). The required AJAX nonce is publicly exposed in frontend HTML, allowing unauthenticated attackers to exploit this SSRF to access internal or private network resources, including cloud metadata services like AWS instance metadata. Additionally, a secondary SSRF vector exists through image URLs fetched from attacker-controlled JSON responses, enabling chained exploitation. The vulnerability affects versions up to 1.1.1 and has a CVSS 3.1 base score of 5.4, indicating medium severity. The service is cloud-hosted, and a patch is available.
Potential Impact
An unauthenticated attacker can exploit this SSRF vulnerability to make server-side HTTP requests to arbitrary internal or external destinations. This may expose sensitive internal services, cloud metadata endpoints (e.g., AWS instance metadata), localhost services, and other resources not intended to be publicly accessible. The secondary SSRF vector increases the attack surface by allowing chained requests through crafted JSON payloads. The impact includes potential information disclosure and reconnaissance within internal networks or cloud environments.
Mitigation Recommendations
A patch is available for this vulnerability. Since the affected product is a cloud-hosted service, the vendor manages remediation server-side. Users should verify with the vendor advisory that the patch has been applied. No additional action is required if the vendor confirms mitigation. If not confirmed, users should avoid using affected plugin versions and monitor vendor communications for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-04-15T20:12:37.007Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a0d1a61ba1db473621f7acc
Added to database: 05/20/2026, 02:20:17 UTC
Last enriched: 05/20/2026, 02:48:37 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 64
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.