{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6394 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6394 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6394 is a medium-severity server-side request forgery vulnerability in wpdive Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor \u0026 FSE, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6394 and fix it if it is affected.\n\nWhat it is: CVE-2026-6394 is a medium-severity server-side request forgery vulnerability in wpdive Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor \u0026 FSE, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6394 in the wild and no public exploit code.\n\nAffected product: wpdive Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor \u0026 FSE. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-6394/ (Markdown: https://insights.sbomify.com/CVE-2026-6394/index.md)","id":"CVE-2026-6394","markdown":"https://insights.sbomify.com/CVE-2026-6394/index.md","name":"CVE-2026-6394","record":{"aliases":["GHSA-88c3-g468-4jgg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit SSRF in Nexa Blocks to access internal services and cloud metadata via exposed nonces and unvalidated URL parameters.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Nexa Blocks \u003c= 1.1.1 - Unauthenticated Blind Server-Side Request Forgery via 'demo_json_file' Parameter","id":"CVE-2026-6394","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Word 2 Cash \u003c= 0.9.2 - Cross-Site Request Forgeryto Stored Cross-Site Scripting via Settings Page","id":"CVE-2026-6395"},"packages":[],"prev":{"headline":"BetterDocs \u003c= 4.3.11 - Missing Authorization to Authenticated (Subscriber+) Unauthorized AI API Usage","id":"CVE-2026-6393"},"products":["Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor \u0026 FSE"],"published":"2026-05-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["wpdive"]},"summary":"Unauthenticated attackers can exploit SSRF in Nexa Blocks to access internal services and cloud metadata via exposed nonces and unvalidated URL parameters.","url":"https://insights.sbomify.com/CVE-2026-6394/"}