CVE-2026-125294 is a critical privilege escalation flaw in the Nexter Blocks Pro WordPress plugin. Attackers who are not logged in can use it to register a new account that holds the full Administrator role.
What Is It
The flaw is in the plugin's tpgb_ajax_register_user() function. The plugin checks the tpgb_acf_key[] and tpgb_acf[] parameters against a byte-level denylist. That denylist misses Unicode look-alike characters, such as U+1E87 and U+00E7 in a key like ẇp_çapabilities, because their UTF-8 bytes don't match any ASCII-based pattern.
The database's default accent-insensitive collation (utf8mb4_unicode_ci / utf8mb4_0900_ai_ci) treats that altered key as the same as the real wp_capabilities row. As a result, update_user_meta() overwrites the new user's role with administrator.
Wordfence classifies the weakness as CWE-269 (Improper Privilege Management).
Why It Matters
- CVSS 3.1: 9.8 (CRITICAL), vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Access needed: none. No authentication or user interaction is required.
- Impact: an attacker with Administrator access controls the whole site. They can install plugins, modify files and execute arbitrary code.
- Ease of exploitation: the nonce the handler requires is published on any page that contains the
tp-login-registerblock. According to the record, the full chain takes three steps: retrieve the nonce, send one crafted registration POST, then log in through the plugin's ownautologinflow. It is "trivially reachable on any default install where user registration is enabled."
The supplied data has no CISA KEV entry for this CVE, so active exploitation is not confirmed by KEV at this time.
What's Vulnerable
- Vendor: POSIMYTH
- Product: Nexter Blocks Pro (WordPress plugin)
- Affected versions: all versions up to and including 5.0.10
- Condition for exploitation: user registration is enabled and a page contains the
tp-login-registerblock
The NVD record lists no CPEs. Its status is "Deferred."
Patch Status
The supplied NVD record doesn't name a fixed version. It only says that all versions up to and including 5.0.10 are affected. No CISA required action exists because the CVE isn't in KEV.
Administrators running Nexter Blocks Pro 5.0.10 or earlier should check the vendor site and the Wordfence advisory below for fix availability. Sites with user registration enabled are exposed under the conditions the record describes.