User Frontend: AI Powered Frontend Post Submission, User Directory, User Profile, Membership & User Registration < 4.3.8 - Missing Authorization to Unauthenticated Media Attachment Deletion
Strategic Overview
- Status
- Patched in 4.3.8
- Affected Plugin
- User Frontend: AI Powered Frontend Post Submission, User Directory, User Profile, Membership & User Registration
- Affected Version
< 4.3.8- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-14568
At a glance
CVE-2026-14568 is a medium-severity Missing Authorization vulnerability in the User Frontend WordPress plugin, affecting versions < 4.3.8. 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 kimsunghoon.
Vulnerability Overview
The User Frontend: AI Powered Frontend Post Submission, User Directory, User Profile, Membership & User Registration plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to 4.3.8 (exclusive). This makes it possible for unauthenticated attackers to delete arbitrary attachment files.
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-862: Missing Authorization
Reaching this weakness in User Frontend < 4.3.8 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For User Frontend the fix is 4.3.8: builds < 4.3.8 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
- 5.4CVE-2025-58672: WP User Frontend <= 4.1.12 Missing Authorization
CVE-2025-58672 - 5.3CVE-2026-12406: User Frontend Unauthenticated Arbitrary Attachment
CVE-2026-12406 - 5.3CVE-2026-57334: User Frontend Missing Authorization
CVE-2026-57334 - 5.3CVE-2026-42412: User Frontend Missing Authorization
CVE-2026-42412
Other vulnerabilities in User Frontend: AI Powered Frontend Post Submission, User Directory, User Profile, Membership & User Registration
- 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