WordPress security changelog
HIGH CVE-2026-5127 Deferred

User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration: Code execution

User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration is affected by code execution. Exploitation requires an authenticated subscriber account. Successful exploitation can run attacker-controlled code in the WordPress hosting account. The published affected range is <= 4.3.1.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration
Plugin slug
wp-user-frontend
Affected
<= 4.3.1
Safe version
See mitigation notes
Published
May 08, 2026
Weakness
CWE-502 — Deserialization of Untrusted Data

This CVE was published May 08, 2026 and is one of 19 known issues for this plugin.

What to do

Update, patch or deactivate.

No fixed release is identified. Update User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration when a release after 4.3.1 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 4.3.10, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership & User Registration plugin for WordPress is vulnerable to Deserialization of Untrusted Data in versions up to, and including, 4.3.1 This is due to insufficient input validation and type checking on the wpuf_files parameter during form submission, combined with unconditional deserialization via maybe_unserialize() when displaying post content. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary PHP objects, which can be leveraged to execute arbitrary code, delete arbitrary files, or perform other malicious actions if a POP chain is present on the target system.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources