Plugins · nexa-blocks · data as of 2026-11-04
Is Nexa Blocks safe? Known vulnerabilities and latest version
- Status
- Closed 2026-05-14
- Known issues on record
- 5
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate nexa-blocks && wp plugin delete nexa-blocks
Check your version
Known vulnerabilities
5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 5 record(s) do not state which versions are affected.
medium 5.4 CVE-2026-6394 · published 2026-05-20
Server-side request forgery (SSRF) in Nexa Blocks (1.1.1 and older)
- Affected
- 1.1.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
critical 9.8 CVE-2026-25429 · published 2026-03-25
PHP object injection in Nexa Blocks (1.1.1 and older)
- Affected
- 1.1.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Deserialization of Untrusted Data vulnerability in wpdive Nexa Blocks nexa-blocks allows Object Injection.This issue affects Nexa Blocks: from n/a through <= 1.1.1.
medium 6.4 CVE-2025-8624 · published 2025-09-30
Stored cross-site scripting (XSS) in Nexa Blocks (1.1.0 and older)
- Affected
- 1.1.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Nexa Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Google Maps widget in all versions up to, and including, 1.1.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
NVD CVE-2025-8624Wordfence advisoryCode change (fix)wordpress.org
medium 4.9 CVE-2025-30976 · published 2025-06-06
Server-side request forgery (SSRF) in Nexa Blocks (1.1.1 and older)
- Affected
- 1.1.1 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Server-Side Request Forgery (SSRF) vulnerability in wpdive Nexa Blocks nexa-blocks allows Server Side Request Forgery.This issue affects Nexa Blocks: from n/a through <= 1.1.1.
medium 6.5 CVE-2025-30952 · published 2025-06-06
Stored cross-site scripting (XSS) in Nexa Blocks (1.1.0 and older)
- Affected
- 1.1.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdive Nexa Blocks nexa-blocks allows Stored XSS.This issue affects Nexa Blocks: from n/a through <= 1.1.0.
Recent activity
- 2026-05-14 — closed on wordpress.org (Security Issue).
- 2026-05-20 — Server-side request forgery (SSRF) disclosed (CVE-2026-6394), fix version not stated.
- 2026-03-25 — PHP object injection disclosed (CVE-2026-25429), fix version not stated.
- 2025-09-30 — Stored cross-site scripting (XSS) disclosed (CVE-2025-8624), fix version not stated.
Get an email when Nexa Blocks has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Nexa Blocks (nexa-blocks) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Server-side request forgery (SSRF) (2) · Cross-site scripting (XSS) (2) · PHP object injection (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/nexa-blocks (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/nexa-blocks"><img src="https://laskyr.com/plugins/nexa-blocks/badge.svg" alt="Nexa Blocks vulnerability status"></a>