Rontend - Security Vulnerability (CVE-2026-119634)
CVE-2026-119634
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.
CVE-2026-119634
MEDIUM
CVSS 6.3
Published 2026-11-18
Updated 2026-11-18
AI Risk Elevated (62/100)
Active Exploit: No strong signal
Published Exploit: No public exploit references
Priority: P3 Priority
Severity Band
MEDIUM
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N
Affected Components
2
Reference Links
6
AI Risk Engine
Elevated (62/100)
Exploitability
High
Active Exploitation
No strong signal
Published Exploit Status
No public exploit references
AI Context
Machine-generated threat intelligence
AI
Updated 1 day ago
AI enriched 1 day ago (2026-11-20 18:16 UTC)
Technical Summary
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…
Potential Impact
Severity is MEDIUM (CVSS 6.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as High based on remote code execution potential.
Primary risk drivers: remote code execution potential
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
AI risk score 62/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.