CVE-2026-95523

User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission <= 4.3.11 - Authenticated (Subscriber+) Subscription Gate Bypass on Post Submission

2026-09-23 00:00
Ananda Dhakal

At a glance

CVE-2026-95523 is a medium-severity Improper Authorization vulnerability in the User Frontend WordPress plugin, affecting versions <= 4.3.11. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.3.12; sites on affected versions should update now. Disclosed September 2026, reported by Ananda Dhakal.

Vulnerability Overview

The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 4.3.11. This is due to missing validation that the caller-supplied form_id refers to an actual wpuf_forms post, and server-side submission status being determined from a client-controlled field rather than post meta. This makes it possible for authenticated attackers, with subscriber-level access and above, to create posts while bypassing subscription and payment gates by supplying a non-form post ID as the form_id parameter, or by manipulating the submission-status field to skip the posting-quota check entirely.

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 interaction from a victim user.

CWE-285: Improper Authorization

Reaching this weakness in User Frontend <= 4.3.11 takes an account at Subscriber level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For User Frontend the fix is 4.3.12: builds <= 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. 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

Related records

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