CVE-2026-75823

User Frontend 3.5.29 - 4.3.11 - Unauthenticated Privilege Escalation

2026-09-28 00:00
Murad Akhmedov

Strategic Overview

Status
Patched in 4.3.12
Affected Plugin
User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
Affected Version
3.5.29 – 4.3.11
CVSS
7.3High
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2026-75823
View all User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission vulnerabilities

At a glance

CVE-2026-75823 is a high-severity Improper Privilege Management vulnerability in the User Frontend WordPress plugin, affecting versions 3.5.29 – 4.3.11. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.12; sites on affected versions should update now. Disclosed September 2026, reported by Murad Akhmedov.

Vulnerability Overview

The User Frontend plugin for WordPress is vulnerable to Privilege Escalation in versions 3.5.29 through 4.3.11. This is due to insufficient restriction on the capabilities a user may grant themselves. This makes it possible for unauthenticated attackers to elevate their privileges beyond those intended for their role.

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-269: Improper Privilege Management

Reaching this weakness in User Frontend 3.5.29 – 4.3.11 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For User Frontend the fix is 4.3.12: builds 3.5.29 – 4.3.11 are affected, anything from 4.3.12 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-75823https://www.wordfence.com/threat-intel/vulnerabilities/id/4799bb1f-4e5d-4b39-9f99-ffb46de4c232https://nvd.nist.gov/vuln/detail/CVE-2026-75823

Related records

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