weDevs WP User Frontend Plugin up to 4.3.1 on WordPress authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in weDevs WP User Frontend Plugin up to 4.3.1 on WordPress. This impacts an unknown function. Performing a manipulation results in authorization. This vulnerability is known as CVE-2026-42412. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in weDevs WP User Frontend Plugin up to 4.3.1 on WordPress. It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity, and availability. The summary by CVE is:
Missing Authorization vulnerability in weDevs WP User Frontend allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP User Frontend: from n/a through 4.3.1.
The weakness was published by Sajjad Haqi. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-42412 since 04/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/06/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202604-5692). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.5
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (Patchstack): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/27/2026 CVE reserved04/29/2026 Advisory disclosed
04/29/2026 VulDB entry created
05/06/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Sajjad Haqi
Status: Not defined
CVE: CVE-2026-42412 (🔒)
GCVE (CVE): GCVE-0-2026-42412
GCVE (VulDB): GCVE-100-360105
CNNVD: CNNVD-202604-5692 - WordPress plugin WP User Frontend 安全漏洞
Entry
Created: 04/29/2026 10:47Updated: 05/06/2026 22:26
Changes: 04/29/2026 10:47 (63), 04/30/2026 23:34 (6), 05/01/2026 23:34 (1), 05/02/2026 22:28 (1), 05/03/2026 18:34 (1), 05/05/2026 00:44 (1), 05/05/2026 20:02 (1), 05/06/2026 22:26 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.