Home › Vulnerabilities

weDevs User Frontend plugin for WordPress Flaw CVE-2026-120070: Update Now

Published October 31, 2026 · Last updated October 31, 2026

WordPress CVE Patch

The short version: CVE-2026-120070 is a high-severity security flaw in weDevs User Frontend plugin for WordPress. The National Vulnerability Database (NVD) published it on October 31, 2026, and the score it lists is 8.8 out of 10. When FraudMeNot checked on October 31, 2026, CISA had not added CVE-2026-120070 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-120070

The record was filed by wordfence.com. In its own words: "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."

Why User Frontend plugin for WordPress admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on wordfence.com rated CVE-2026-120070 8.8 (High) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping User Frontend plugin for WordPress running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Affected User Frontend plugin for WordPress releases

According to the record, these releases are vulnerable:

  • 0 through 4.3.13

The type of bug behind CVE-2026-120070

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-269, Improper Privilege Management. MITRE describes this class of bug as follows: "The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor."

Vendor remediation for CVE-2026-120070

The vendor advisory remediation for operators of User Frontend plugin for WordPress, quoted for this page, is: "Update WP User Frontend to version 4.3.14 or later. Its 4.3.14 changelog (October 28, 2026) lists a fix, reported by Wordfence, for members placing the registration shortcode in a submission to give themselves a higher role. After updating, look for unexpected Editor accounts and for published posts that contain a wpuf-registration shortcode."

What to do about it

  • Update now: Update WP User Frontend to version 4.3.14 or later. Its 4.3.14 changelog (October 28, 2026) lists a fix, reported by Wordfence, for members placing the registration shortcode in a submission to give themselves a higher role. After updating, look for unexpected Editor accounts and for published posts that contain a wpuf-registration shortcode.
  • Who should act: IT teams, managed service providers, and developers who run or ship User Frontend plugin for WordPress. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from weDevs (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from October 31, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-120070. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-120070 record details from CISA and NVD

  • Attack complexity for CVE-2026-120070: low
  • CVE-2026-120070 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-120070: exploitability 2.8, impact 5.9.
  • Who mapped the weakness type: the address listed on wordfence.com (Primary)
  • References in the NVD record: 6.

Dates to know

  • October 31, 2026: NVD publishes CVE-2026-120070.
  • October 31, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-120070 is not listed.
  • October 31, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.