What happened
A critical vulnerability, CVE-2026-125294, affects the paid Nexter Blocks Pro plugin for WordPress. The plugin adds dozens of page-building blocks to the Gutenberg editor, including a user login and registration block.
The flaw was described by Wordfence, a security company focused on WordPress, and the record was published in the NVD database on November 21, 2026. The bug sits in the function that handles new user registrations: an attacker can give themselves the administrator role instead of a regular user role. All versions up to and including 5.0.10 are affected.
The NVD record does not say which version fixes the issue or when the vendor announced it. The flaw is not in the CISA KEV catalog, and the EU vulnerability database EUVD (entry EUVD-2026-132560) lists no active exploitation. Wordfence describes the attack as easy to carry out, though, so do not put off the update.
Why it is dangerous
This is a privilege escalation flaw (CWE-269, improper privilege management). The plugin keeps a list of fields a new user must not set during registration, such as their own role. The check, however, only compares exact characters. A field name written with look-alike accented letters slips past it, and the database, with its common default settings, treats it as the very same field.
Think of a doorman with a list of banned names who compares them letter by letter. Someone who signs in as “Ádmin” instead of “Admin” gets through, and the filing clerk then files them under the same name.
- The attacker needs no login and attacks over the internet.
- According to Wordfence, the site must have user registration enabled and a page with the plugin’s login and registration block. A single crafted registration is then enough, and the plugin logs the attacker in automatically.
- The result is full administrator access: installing plugins, modifying files and running their own code on the server within the site’s permissions.
The CVSS score of 9.8 out of 10 (CVSS 3.1) was assigned by Wordfence. CVSS is an international severity scale, and 9.8 falls into the top “critical” band. The CISA KEV catalog lists flaws that the US agency CISA knows are exploited in real attacks. This one is not on it yet. An EPSS exploitation probability estimate is not available yet.
Who is affected
This affects WordPress sites running Nexter Blocks Pro version 5.0.10 or older. According to Wordfence, the attack is directly reachable on sites that have user registration enabled and use the Nexter Blocks login and registration block somewhere (internally tp-login-register).
Typical examples are company websites, online shops, member areas and organisation sites on ordinary web hosting, often built by an agency or an outside contractor. If someone else manages your site, ask them.
The NVD record mentions only the Pro version. It does not mention the free Nexter Blocks, the Nexter theme or Nexter Extension. Sites without registration enabled should still not delay the update.
How to check if you are affected
In the WordPress dashboard, open Plugins and find Nexter Blocks Pro. The version is shown under the plugin name. If you have WP-CLI on the server, the following commands change nothing and only print information:
wp plugin list --fields=name,title,version,status | grep -i nexter
To see whether registration is enabled, go to Settings > General and look at “Membership” (Anyone can register). Or run this command, where a result of 1 means registration is on:
wp option get users_can_register
If you manage several sites, check all of them, including old campaign and test sites.
How to fix it
The NVD record does not name a specific fixed version. Details are in the Wordfence advisory (linked from the NVD record) and from the vendor at nexterwp.com. Follow these steps:
- Back up the site, both files and database.
- Make sure your licence is active. The vendor states on its website that updates stop once a licence expires.
- Update Nexter Blocks Pro to the latest version via Plugins or by uploading the package from your NexterWP customer account.
- Confirm that the installed version is newer than 5.0.10 and that the vendor or Wordfence lists it as fixed.
- Go through the checks in the section on possible compromise.
The NVD record lists no vendor workaround. Until you have the fix, we recommend general precautions: turn off user registration in Settings > General, remove the login and registration block from your pages, or temporarily deactivate the plugin. Deactivating it may break the layout of pages that use its blocks.
Order of work: sites with registration enabled first, then the rest. CISA has not added the flaw to the KEV catalog, so it has issued no required action for it.
What if you may already be compromised
The main sign of an attack is a new administrator account that nobody on your team created. You can find it under Users > All Users with the Administrator filter, or with this read-only command:
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
The NVD record lists no specific indicators of compromise. Look in particular for:
- unknown or recently installed plugins and themes
- new PHP files in
wp-content/uploads, where they do not belong - unusual POST requests to
admin-ajax.phpin the server logs shortly before an unknown account appeared
Run the following command from the WordPress root folder. It only lists all PHP files in the uploads folder along with their last modification date:
find wp-content/uploads -type f -iname '*.php' -ls
If you find an unknown administrator, first note down its details and creation time. An attacker with that level of access may have left a backdoor, so bring in an incident response specialist, change all passwords and consider restoring from a backup made before the attack. If the site processes personal data, assess whether you must report the incident under GDPR.