Quick answers
- Is CVE-2026-120070 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120070 being exploited in the wild.
- How severe is CVE-2026-120070?
- High severity, with a CVSS score of 8.8, published 31 October 2026.
- Which products and versions are affected?
- WP User Frontend up to and including 4.3.13.
- Is there a fix for CVE-2026-120070?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-120070 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120070?
- Check whether you run WP User Frontend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the `submit_post()` function's handling of the `post_content` parameter. The plugin uses inconsistent validation: it checks for blocked shortcodes against a sanitized copy of the post content, but persists a different version processed through `wp_kses()`, which strips C0 control bytes. An attacker can inject a single `\x01` byte inside the `[wpuf-registration]` tag name to bypass the blocklist check via `strpos()`. The shortcode then functions normally in the database, and since the Frontend container only instantiates on non-admin pages, the shortcode is rendered on frontend pages. Authenticated Subscriber-level users can exploit this to inject an Editor-role registration form that creates privileged accounts, especially when `autologin_after_registration` is enabled.
Affected products
- WP User Frontend WP User Frontend up to and including 4.3.13
Timeline
- 2026-10-31: disclosed