CVE-2026-6394
Received Received - Intake
Server-Side Request Forgery in Nexa Blocks WordPress Plugin

Publication date: 2026-05-20

Last updated on: 2026-05-20

Assigner: Wordfence

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-20
Last Modified
2026-05-20
Generated
2026-05-20
AI Q&A
2026-05-20
EPSS Evaluated
N/A
NVD
CVE-2026-6394
EUVD
EUVD-2026-31033
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
nexa_blocks nexa_blocks to 1.1.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Nexa Blocks plugin for WordPress is vulnerable to Server-Side Request Forgery (SSRF) in versions up to and including 1.1.1. This happens because the import_demo() function accepts a user-supplied URL through the demo_json_file POST parameter and uses it directly in a server-side HTTP request without validating or restricting the URL. Additionally, a security nonce intended to protect this action is publicly exposed on the frontend, allowing unauthenticated attackers to exploit this vulnerability.

As a result, attackers can make the server send HTTP requests to arbitrary internal or external destinations, including internal services, cloud metadata endpoints like AWS instance metadata, localhost services, and other resources that should not be publicly accessible. There is also a secondary SSRF vector where image URLs from the attacker-controlled JSON response are fetched by the server, enabling chained exploitation.


How can this vulnerability impact me? :

This vulnerability can allow unauthenticated attackers to make the server perform HTTP requests to internal or external systems that are normally inaccessible. This can lead to exposure of sensitive internal services, cloud metadata endpoints, and other protected resources.

Such unauthorized access can result in information disclosure, potential further exploitation of internal systems, and compromise of the server's security posture.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart