CVE-2026-125294 Security Alert: CRITICAL Vulnerability

Urgent: CVE-2026-125294 requires immediate attention.

· 7 min read

Executive Summary

CVE-2026-125294 is a critical privilege-escalation flaw in the Nexter Blocks Pro WordPress plugin, affecting all versions up to and including 5.0.10. An unauthenticated attacker can register a new account and, with a crafted request, have that account promoted to Administrator. From there, the attacker can install plugins, change site content, modify files, and potentially execute arbitrary code.

This issue is especially dangerous for solo developers and small teams because the exploit path is simple, does not require prior access, and works on default installs where user registration is enabled. Although there are no reports of in-the-wild exploitation and it is not in CISA KEV at this time, the severity is CRITICAL (CVSS 9.8) and should be treated as an emergency.

Immediate Action

  • Patch immediately to the first fixed release from the vendor. If the fixed version is not yet confirmed, remove or disable Nexter Blocks Pro until a safe version is available. TODO: insert vendor advisory / fixed version link
  • Disable public registration in WordPress if you do not explicitly need it: Settings > General > Membership and uncheck “Anyone can register.”
  • Temporarily deactivate the tp-login-register block or the entire plugin on production sites until patched.
  • Review existing Administrator accounts for unexpected additions, especially recently created users.
  • Rotate admin passwords and application secrets if you suspect any exposure.
  • Take a backup before changes, but do not delay patching while waiting for a maintenance window.

Affected Versions

  • nexter-blocks-pro@<=5.0.10 vulnerable
  • nexter-blocks-pro@TODO-fixed-version safe once vendor patch is applied
  • If you cannot confirm the fixed release, treat all installed copies up to 5.0.10 as unsafe and remove or disable them

Resolution Guide

WordPress / plugin remediation

# If installed via WP-CLI, deactivate immediately
wp plugin deactivate nexter-blocks-pro

# Remove the plugin if you do not need it
wp plugin delete nexter-blocks-pro

# Update once a fixed version is confirmed by the vendor
wp plugin update nexter-blocks-pro

# Check installed version
wp plugin list --fields=name,status,version | grep -i nexter

Config hardening

# Disable user registration in wp-config.php is not a direct setting,
# so use the admin UI or a hardening plugin.
# Recommended operational controls:
# - Turn off public registration
# - Remove the tp-login-register block from pages
# - Restrict admin access by IP/VPN if feasible

Rollback guidance

# If the plugin update causes issues, roll back only after disabling the vulnerable feature
wp plugin deactivate nexter-blocks-pro
wp plugin install nexter-blocks-pro --version=TODO-safe-version --force

Docker / containerized WordPress

# Rebuild the image with the patched plugin version baked in
docker build --no-cache -t yourorg/wordpress:patched .

# Or redeploy using a known-good image tag
docker pull yourorg/wordpress:TODO-safe-tag
docker stop wordpress && docker rm wordpress
docker run -d --name wordpress yourorg/wordpress:TODO-safe-tag

Linux package managers

# WordPress plugins are usually not managed by apt/yum directly,
# but if your deployment packages them, update the site artifact or image.
sudo apt update
sudo apt upgrade
sudo yum update

JavaScript / Python / Java ecosystems

This issue is specific to a WordPress plugin, so npm/pip/Maven/Gradle are not the normal delivery path. If your team mirrors WordPress assets into application bundles, update the site package or container image rather than a language dependency.

Minimal code fix example (illustrative only)

// Replace byte-level denylist checks with strict allowlisting of expected ASCII keys
$allowed = array('wp_capabilities', 'wp_user_level');

foreach ($incoming_keys as $key) {
    if (!in_array($key, $allowed, true)) {
        continue;
    }
    update_user_meta($user_id, $key, $value);
}

Detection & Verification

Check whether you are vulnerable

# WordPress CLI version check
wp plugin list --fields=name,version,status | grep -i 'nexter-blocks-pro'

# File-based check if WP-CLI is unavailable
grep -Rni "tpgb_ajax_register_user\|tpgb_acf_key\|tpgb_acf" wp-content/plugins/nexter-blocks-pro/

Look for suspicious admin accounts

# List users with administrator role
wp user list --role=administrator --fields=ID,user_login,user_email,registered

# Review recent registrations
wp user list --orderby=registered --order=desc --fields=ID,user_login,user_email,registered

Verify the fix

# Confirm the plugin version is above the vulnerable range
wp plugin list --fields=name,version,status | grep -i 'nexter-blocks-pro'

# Confirm public registration is disabled
wp option get users_can_register

# Confirm the vulnerable handler is no longer reachable in the plugin codebase
grep -Rni "tpgb_ajax_register_user" wp-content/plugins/nexter-blocks-pro/ || echo "Handler not found"

Additional checks

  • Search web server logs for POST requests to registration endpoints tied to the plugin.
  • Review any newly created Administrator account for creation time and IP address.
  • If you use a WAF, add temporary rules to block registration requests containing unusual Unicode in meta keys.

Risk and Impact

Successful exploitation gives the attacker a full Administrator account on the WordPress site. That typically means complete site takeover: plugin installation, theme edits, file changes, content manipulation, credential theft, and possible remote code execution through the admin interface or malicious plugins.

For small teams, the blast radius can include defacement, SEO spam, malware distribution, customer data exposure, and loss of trust. Because the exploit is unauthenticated and the nonce is exposed on pages containing the registration block, the attack path is low-friction and should be treated as urgent.

Keep reading