Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-95523Published · Updated

Action summary

Affected: ≤4.3.11Update to 4.3.12 or newer

All remediation steps
Severity
Medium6.3
CVSS
6.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-285 Improper Authorization
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission wp-user-frontend

  1. Affected≤ 4.3.11
  2. Patched in4.3.12

Update to 4.3.12 or newer.

You are affected if you run ≤ 4.3.11. Version 4.3.12 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 4.3.12, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Ananda Dhakal.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission

All 43
More vulnerabilities in User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Taxonomy Field Text-Input
≤4.3.13Update to 4.3.14
CVE-2026-109214
Medium6.1Reflected Cross-Site Scripting via 'field_attr[required]' Parameter
≤4.3.13Update to 4.3.14
CVE-2026-103962
High8.8Authenticated (Subscriber+) Privilege Escalation via post_content Parameter
≤4.3.13Update to 4.3.14
CVE-2026-120070
Medium4.3Missing Authorization
≤4.3.13Update to 4.3.14
CVE-2026-52708
Medium5.3Missing Authorization
≤4.3.13Update to 4.3.14
CVE-2026-48884

Timeline

  1. CVE published

    Severity medium, CVSS 6.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?