Live › vulnerability › CVE-2026-120070
The User Frontend WordPress plugin up to and including 4.3.13 lets a logged-in Subscriber store a registration shortcode in a published post by hiding a control byte in its tag name, which bypasses the plugin's blocklist check. Any visitor can then submit the resulting public form to create an Editor-role account, and when autologin after registration is enabled, that account is logged in immediately.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 08:34 UTC. All times on this page are UTC.
Sites running the User Frontend plugin up to and including 4.3.13 are exposed, and the attack only needs any Subscriber-level account on the site. The worst case the sources describe depends on autologin after registration being enabled, which is the default. Sites without the plugin, or with autologin disabled and no way for Subscribers to log in, are less exposed.
No product ranges from the sources yet.
4.3.13 are affected.autologin_after_registration is enabled in the plugin's settings.[wpuf-registration with role="editor" in the content.No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.3.13 via the post_content parameter of the submit_post() function. The vulnerability exists because the protected-shortcode blocklist guard inspects the sanitize_textarea_field() copy of the submitted post_content, while the copy actually persisted to the database is processed through wp_kses(), whose wp_kses_no_null() step strips C0 control bytes — allowing an attacker to inject a single \x01 byte inside the [wpuf-registration] tag name to defeat the strpos() blocklist check while the clean, functional shortcode is stored verbatim; strip_shortcodes() does not neutralize the stored shortcode either, because the Frontend container that registers it via add_shortcode() is only instantiated when is_admin() is false, and admin-ajax requests have is_admin() === true. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a [wpuf-registration role="editor"] shortcode into a published post, causing a live Editor-role registration form to be rendered publicly on the frontend that any visitor — or the attacker themselves — can submit to mint a WordPress Editor account with an immediately active privileged session when the default autologin_after_registration setting is enabled.
This page as .md · .json · in your agent: get_signal("CVE-2026-120070")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.