Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister/obtain subscriber account
-
DeliveryAccess paywalled post-creation form
-
ExploitSubmit without subscription purchase
-
ExecutionPost created and auto-published
-
ImpactPaywall/revenue control bypassed
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account at subscriber level or above (PR:L) on a WordPress site running WP User Frontend before 4.3.12 that uses the plugin's subscription-gated post-creation forms. The specific prerequisite is a form configured to restrict posting to paying subscribers; the vulnerable post-creation handler fails to enforce that subscription-purchase requirement. Whether the created post is immediately published versus held for moderation depends on the individual form's publish configuration, which limits impact on forms set to draft/pending review. Exploitation is further limited by the need for any valid low-privilege account (so sites that disable open registration raise the bar) and by the bounded integrity-only impact (no data disclosure, no availability loss). |
| Impact | This is a genuinely low-to-moderate priority issue despite publicly available exploit code. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) scores 4.3 (Medium) and is internally consistent with the description: network-reachable, low complexity, but requiring low-level authentication (PR:L, i.e. subscriber-level account) and yielding only limited integrity impact (I:L) with no confidentiality or availability effect. The flaw is a broken-authorization/subscription-bypass issue, not a code-execution or data-exposure bug. A public exploit exists (per WPScan/cveorg reference), which raises practical exploitability, but there is NO EPSS score provided and NO CISA KEV listing, so there is no evidence of active exploitation - the signals do not conflict, they simply point to a low-severity integrity bug that is easy to trigger by any registered user but has bounded impact. Note the tag 'Information Disclosure' contradicts the CVSS vector (C:N), which indicates NO confidentiality impact; the real impact is unauthorized content creation/publishing, an integrity concern. The main risk is business-logic/revenue abuse (bypassing a paywall) rather than a security compromise of the host. |
| Exploit ScenarioDerived | An attacker registers (or uses an existing) subscriber-level account on a WordPress site running WP User Frontend with a subscription-gated posting form. Instead of purchasing the required subscription, they submit the vulnerable post-creation handler directly, creating - and, depending on form configuration, immediately publishing - posts reserved for paying subscribers. A public exploit is available via WPScan, and the low complexity (AC:L) with only subscriber access (PR:L) makes this trivial to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Authenticated users holding subscriber-level access or above can bypass the subscription-purchase requirement enforced by WP User Frontend before version 4.3.12, creating posts through forms that are intended to be reserved for paying subscribers - and, depending on how the individual form is configured, having those posts published immediately rather than held for review. The issue is rated CVSS 3.1 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), reflecting a bounded integrity-only impact with no confidentiality or availability loss, and publicly available exploit code exists. Practical risk is low-to-moderate: an attacker needs a valid low-privilege account on an affected WordPress site that actually uses the plugin's subscription-gated post-creation forms, and sites that disable open registration raise that bar further.
RemediationAI
Upgrade WP User Frontend to version 4.3.12 or later - vendor-released patch: 4.3.12 - which restores the subscription-purchase entitlement check in the affected post-creation handler; full details are in the WPScan advisory at https://wpscan.com/vulnerability/a11bf097-3829-4baa-878c-80b113c5a744/. Where an immediate update is not possible, the most effective compensating control is to disable open user registration or otherwise restrict who can obtain a subscriber-level account, since every exploit path in the assessment depends on an attacker holding a valid low-privilege login; the trade-off is that this blocks legitimate self-service signups on sites that rely on them. A second option is to reconfigure the subscription-gated post-creation forms so all submissions are held as drafts or pending review rather than published on submission - this neutralizes the immediate-publication outcome but does not stop unauthorized post creation, and it may alter editorial workflows. Administrators can also temporarily unpublish or disable the affected subscription-gated submission forms entirely, accepting the loss of that self-service feature, and should audit existing content for posts authored by subscriber accounts that should not have been able to submit. Routine measures such as restricting the subscriber role's capabilities via a role-management plugin reduce blast radius but should be treated as defense in depth rather than a substitute for patching to 4.3.12. No vendor patch is described as unavailable in the source data; the 4.3.12 release is the confirmed fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WP User Frontend is a WordPress plugin that exposes front-end post submission forms, commonly paired with a paid-subscription or membership gate so that only paying customers can create and publish content. The defect sits in one of the plugin's post-creation handlers, which fails to perform the same subscription-purchase entitlement check that the rest of the plugin applies before accepting a submission. This is a missing-authorization-check weakness class (functionally equivalent to CWE-862), where the access-control decision is absent from a specific request path rather than being incorrectly implemented - the classic 'one handler forgot the guard' pattern in plugin code. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N confirms the flaw is remotely reachable over the network with low attack complexity, requires an authenticated principal at subscriber level (PR:L), needs no user interaction, and yields only a limited integrity impact - an unauthorized post is created and potentially published, but no data is exposed or destroyed. Whether an attacker achieves immediate publication or merely an unauthorized draft/pending entry is governed by the target form's publish configuration, so the realized impact varies site by site. The affected CPE entry (cpe:2.3:a:unknown:wp_user_frontend:*:*:*:*:*:*:*:*) indicates all versions before the 4.3.12 fix are in scope, with vendor attribution not resolved in the feed data.
Know when Wp User Frontend gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Any subscriber-level account suffices, so PR:L and AC:L over the network (AV:N); impact is unauthorized content creation only, giving I:L with C:N and A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The WP User Frontend WordPress plugin before 4.3.12 does not enforce its subscription-purchase requirement in one of its post-creation handlers, allowing authenticated users with subscriber-level access and above to create and, depending on the form's configuration, immediately publish posts through forms restricted to paying subscribers.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Wp User Frontend
View allPHP Object Injection in the WP User Frontend WordPress plugin (versions ≤ 4.3.10) allows any subscriber-level authentica
A missing authorization vulnerability exists in weDevs WP User Frontend plugin through version 4.2.8, allowing attackers
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs WP User Fro
Broken access control in WP User Frontend plugin for WordPress (versions <= 4.3.7) allows unauthenticated remote attacke
WP User Frontend plugin for WordPress (versions through 4.3.1) exposes a Missing Authorization flaw that allows unauthen
Improper access control in WP User Frontend through version 4.2.5 allows authenticated users to modify content they shou
Arbitrary file deletion in WP User Frontend (weDevs) versions up to and including 4.3.11 allows an authenticated Subscri
WP User Frontend versions up to and including 4.3.11 contain an authentication bypass by spoofing that allows an authent
Unauthenticated attackers can bypass an access-control mechanism in the WordPress plugin WP User Frontend at version 4.3
EUVD-2026-91209
GHSA-5f7g-qp7c-jr44
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB