WordPress plugin · Updated daily · Source: Wordfence Intelligence

Nexter Blocks vulnerabilities: affected versions and fixes

Nexter Blocks has 9,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Nexter Blocks at a glance

  • 16 publicly disclosed vulnerabilities. The most recent was disclosed on Nov 17, 2026.
  • Ranked #2193 by popularity on WordPress.org (9,000+ active installs).
  • The latest version is 5.0.11 (released Nov 17, 2026). The most recent security fix shipped in 5.0.11.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Nexter Blocks version

Enter the Nexter Blocks version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Nexter Blocks”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Nexter Blocks”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (5.0.11). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Nexter Blocks vulnerabilities

  • Nexter Blocks <= 5.0.10 - Missing Authorization to Authenticated (Contributor+) Arbitrary Modification via MCP Ability create-/update-/delete-tpgb-button-preset

    Missing authorization · CVE-2026-130034

    Affected versions: ≤ 5.0.10

    Fixed in: 5.0.11

    Severity: Medium 4.3 · Disclosed Nov 17, 2026

  • Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder <= 5.0.10 - Missing Authorization

    Missing authorization · CVE-2026-129064

    Affected versions: ≤ 5.0.10

    Fixed in: 5.0.11

    Severity: Medium 4.3 · Disclosed Nov 17, 2026

  • Nexter Blocks <= 5.0.1 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-15678

    Affected versions: ≤ 5.0.1

    Fixed in: 5.0.2

    Severity: Medium 6.4 · Disclosed Aug 3, 2026

  • Nexter Blocks <= 5.0.1 - Payment Bypass to Authenticated (Contributor+) Stored CSS Injection

    Other weakness · CVE-2026-17011

    Affected versions: ≤ 5.0.1

    Fixed in: 5.0.2

    Severity: Medium 4.3 · Disclosed Aug 3, 2026

  • Nexter Blocks <= 5.0.0 - Authenticated (Subscriber+) Path Traversal to Arbitrary CSS/JS File Deletion via 'plus_name' Parameter

    Arbitrary file read or deletion · CVE-2026-15420

    Affected versions: ≤ 5.0.0

    Fixed in: 5.0.1

    Severity: Medium 4.3 · Disclosed Jul 23, 2026

  • Nexter Blocks <= 4.7.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'commentIcon' Block Attribute

    Cross-site scripting (XSS) · CVE-2026-6740

    Affected versions: ≤ 4.7.4

    Fixed in: 4.7.5

    Severity: Medium 6.4 · Disclosed Jul 7, 2026

  • Nexter Blocks <= 4.7.0 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-39516

    Affected versions: ≤ 4.7.0

    Fixed in: 4.7.1

    Severity: Medium 5.3 · Disclosed Mar 26, 2026

  • Nexter Blocks <= 4.6.3 - Authenticated (Subscriber+) Information Exposure

    Information disclosure · CVE-2026-24377

    Affected versions: ≤ 4.6.3

    Fixed in: 4.6.4

    Severity: Medium 4.3 · Disclosed Jan 26, 2026

  • Nexter Blocks <= 4.5.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Multiple Widgets

    Cross-site scripting (XSS) · CVE-2025-8567

    Affected versions: ≤ 4.5.4

    Fixed in: 4.5.5

    Severity: Medium 6.4 · Disclosed Aug 18, 2025

  • Nexter Blocks <= 4.5.4 - Missing Authorization

    Missing authorization · CVE-2025-54739

    Affected versions: ≤ 4.5.4

    Fixed in: 4.5.5

    Severity: Medium 5.3 · Disclosed Aug 14, 2025

  • Nexter Blocks <= 4.0.7 - Missing Authorization

    Missing authorization · CVE-2024-56294

    Affected versions: ≤ 4.0.7

    Fixed in: 4.0.8

    Severity: Medium 4.3 · Disclosed Jan 3, 2025

  • Nexter Blocks <= 4.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-56246

    Affected versions: ≤ 4.0.4

    Fixed in: 4.0.5

    Severity: Medium 6.4 · Disclosed Dec 30, 2024

  • Multiple Plugins <= (Various Versions) - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via FancyBox JavaScript Library

    Cross-site scripting (XSS) · CVE-2024-5020

    Affected versions: ≤ 4.3.1

    Fixed in: 4.3.2

    Severity: Medium 6.4 · Disclosed Dec 3, 2024

  • Nexter Blocks <= 3.3.3 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-50452

    Affected versions: ≤ 3.3.3

    Fixed in: 4.0.0

    Severity: Medium 6.4 · Disclosed Oct 24, 2024

  • The Plus Blocks for Block Editor | Gutenberg <= 3.2.5 - Missing Authorization

    Missing authorization · CVE-2024-33572

    Affected versions: ≤ 3.2.5

    Fixed in: 3.2.6

    Severity: Medium 4.3 · Disclosed Apr 25, 2024

  • The Plus Blocks for Block Editor | Gutenberg <= 3.2.5 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-30435

    Affected versions: ≤ 3.2.5

    Fixed in: 3.2.6

    Severity: Medium 6.1 · Disclosed Mar 28, 2024

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 17, 2026.

Most common weaknesses in Nexter Blocks

Cross-site scripting (XSS)

7 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

5 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Information disclosure

2 issues

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Nexter Blocks safe to use?

Nexter Blocks is a well-known plugin with 9,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (5.0.11) and turn on automatic updates.

How do I find which version of Nexter Blocks my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesNexter Blocks on WordPress.org