CVE-2026-119634: User Frontend <= 4.3.14 - Authenticated (Author+) Privilege Escalation to 'post_content' Parameter

Published Nov 18, 2026
·
Updated

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 draftpost() function. This is due to the function storing the postcontent parameter via wpinsertpost() without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling submitpost() handler — a gap that wpkses 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 wpufmodifyshortcodes filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the wpufdraftpost AJAX endpoint carry no editlast post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.

Affected Software

1 affected component
weDevs WP User Frontend<=4.3.14

Event History

Nov 18, 2026
CVE Published
via MITRE·11:30 AM
Data Sourced
via MITRE·11:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated WordPress user with Author-level access or higher can exploit it. The attacker needs to be able to submit a post through the affected frontend post-submission functionality.

2

Does exploitation require a visitor to take action?

Yes. After the attacker embeds the registration shortcode in a post, a site visitor must register through the form rendered from that post. That registrant can then be assigned the Editor role.

3

Are sites protected by the shortcode filtering added in version 4.3.14?

No. The described flaw affects versions through 4.3.14 because the protected-shortcode allow-list check exists in the sibling submit_post() handler but not in draft_post(). The render-time wpuf_modify_shortcodes filter also does not protect posts created through the wpuf_draft_post AJAX endpoint.

4

How can an administrator identify potentially affected content?

Review posts created through the wpuf_draft_post AJAX endpoint for embedded protected registration shortcodes, including [wpuf-registration role="editor"]. The affected posts lack _edit_last post metadata, which causes the render-time shortcode filter to leave their content unchanged.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203