User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration <= 4.3.7 - Insecure Direct Object Reference to Unauthenticated Arbitrary Post Modification via 'wpuf_files_data' Parameter
Strategic Overview
- Status
- Patched in 4.3.8
- Affected Plugin
- User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
- Affected Version
<= 4.3.7- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-12418
At a glance
CVE-2026-12418 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the User Frontend WordPress plugin, affecting versions <= 4.3.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.8; sites on affected versions should update now. Disclosed July 2026, reported by Kim ChanYeop.
Vulnerability Overview
The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.7 via the 'wpuf_files_data' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to overwrite the post_title, post_content, and post_excerpt of any arbitrary post on the site, including posts authored by administrators. Exploitation requires access to any WPUF post submission form; this is achievable by users with no WordPress role, as the wpuf_submit_post AJAX action is gated only by a nonce with no capability check for the downstream post-edit operation.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
User Frontend <= 4.3.7 carries this weakness at wpuf_files_data, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For User Frontend the fix is 4.3.8: builds <= 4.3.7 are affected, anything from 4.3.8 onward is not.
Remediation
Update to version 4.3.8, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: User Frontend 4.3.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
- 9.8WP User Frontend < 2.3.11 Arbitrary File Upload
- 9.1CVE-2024-38693: WP User Frontend <= 4.0.7 SQL Injection
CVE-2024-38693 - 8.8CVE-2026-5127: User Frontend PHP Object Injection
CVE-2026-5127 - 8.8CVE-2026-1565: User Frontend Arbitrary File Upload
CVE-2026-1565 - 8.8CVE-2023-47682: WP User Frontend <= 3.6.5 Privilege Escalation
CVE-2023-47682 - 8.8CVE-2021-25076: WP User Frontend SQL Injection & Reflected XSS
CVE-2021-25076 - 8.1CVE-2021-24649: WP User Frontend <= 3.5.28 Privilege Escalation
CVE-2021-24649 - 7.2WP User Frontend SQL Injection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C