CVE-2025-14047

WP User Frontend <= 4.2.4 - Missing Authorization to Unauthenticated Arbitrary Attachment Deletion

2026-01-01 13:23
shark3y

Strategic Overview

Status
Patched in 4.2.5
Affected Plugin
User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
Affected Version
<= 4.2.4
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-14047
View all User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission vulnerabilities

At a glance

CVE-2025-14047 is a medium-severity Missing Authorization vulnerability in the User Frontend WordPress plugin, affecting versions <= 4.2.4. 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.2.5; sites on affected versions should update now. Disclosed January 2026, reported by shark3y.

Vulnerability Overview

The Registration, User Profile, Membership, Content Restriction, User Directory, and Frontend Post Submission – WP User Frontend plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'Frontend_Form_Ajax::submit_post' function in all versions up to, and including, 4.2.4. This makes it possible for unauthenticated attackers to delete attachment.

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.2.4 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.2.5: builds <= 4.2.4 are affected, anything from 4.2.5 onward is not.

Remediation

Update to version 4.2.5, 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.2.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14047https://www.wordfence.com/threat-intel/vulnerabilities/id/6e95b16f-a25a-45c7-a875-2d34a1e127cehttps://nvd.nist.gov/vuln/detail/CVE-2025-14047

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C