Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
nexa-blocks · plugin
Known security vulnerabilities for Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 critical · 2 exploitable without logging in · latest May 19, 2026
Closed on wordpress.org
Removed from the directory on May 14, 2026 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2026-25429unauthenticated≤ 1.1.1
WordPress Nexa Blocks plugin <= 1.1.1 - PHP Object Injection vulnerability
- Medium 6.5
CVE-2025-30952login required≤ 1.1.0
WordPress Nexa Blocks plugin <= 1.1.0 - Cross Site Scripting (XSS) Vulnerability
- Medium 6.4
CVE-2025-8624contributor+≤ 1.1.0
Nexa Blocks <= 1.1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Google Maps Widget
- Medium 5.4
CVE-2026-6394unauthenticated≤ 1.1.1
Nexa Blocks <= 1.1.1 - Unauthenticated Blind Server-Side Request Forgery via 'demo_json_file' Parameter
- Medium 4.9
CVE-2025-30976login required≤ 1.1.1
WordPress Nexa Blocks plugin <= 1.1.1 - Server Side Request Forgery (SSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).