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.14 via the `draft_post()` function
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium.
Data as of 18 Nov 2026, 13:49 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 6.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wedevsUser Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission | Affected
| Fixed in– |
Description
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.14 via the `draft_post()` function. This is due to the function storing the `post_content` parameter via `wp_insert_post()` without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling `submit_post()` handler — a gap that `wp_kses` filtering does not close, as it strips only HTML tags while leaving shortcode text such as `[wpuf-registration role="editor"]` intact. This makes it possible for authenticated attackers, with Author-level access and above, to embed a registration shortcode in a post and cause any site visitor who subsequently registers through the rendered form to receive Editor-level access. The render-time `wpuf_modify_shortcodes` filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the `wpuf_draft_post` AJAX endpoint carry no `_edit_last` post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.
References
- nvd.nist.gov/vuln/detail/CVE-2026-119634 (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Frontend_Form.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Frontend_Form.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/includes/Frontend/Registration.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-user-frontend/tags/4.3.14/wpuf-functions.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3804840/wp-user-frontend/trunk/includes/Frontend/Frontend_Form.php (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/c747246a-8d3b-4b9f-866a-dece3628cd99?source=cve (opens in a new tab)