shabti Frontend Admin by DynamiApps Plugin up to 3.28.36 on WordPress Configuration wp-admin/post.php feadmin_get_user_roles role privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in shabti Frontend Admin by DynamiApps Plugin up to 3.28.36 on WordPress. The impacted element is the function feadmin_get_user_roles of the file wp-admin/post.php of the component Configuration Handler. The manipulation of the argument role leads to privileges management.
This vulnerability is documented as CVE-2026-6228. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in shabti Frontend Admin by DynamiApps Plugin up to 3.28.36 on WordPress. This issue affects the function feadmin_get_user_roles of the file wp-admin/post.php of the component Configuration Handler. The manipulation of the argument role with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to Privilege Escalation in versions up to and including 3.28.36. This is due to insufficient authorization checks in the role field update mechanism combined with overly permissive capabilities for the admin_form post type. The admin_form custom post type uses 'capability_type' => 'page', which grants editors the ability to create and edit forms. When an editor creates an edit_user form, they can manipulate the form configuration to include 'administrator' in the role_options array by directly submitting POST data to wp-admin/post.php, bypassing the UI restrictions in feadmin_get_user_roles(). When the form is subsequently submitted, the pre_update_value() function in class-role.php only validates that the submitted role exists in the form's role_options array (lines 107-110), but fails to verify that the current user has permission to assign that specific role. This makes it possible for unauthenticated attackers to first register as editors (via a public new_user form), then create an edit_user form with administrator in the allowed roles, and finally use that form to escalate their own privileges to administrator.
The weakness was released by Colin Xu. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-6228 since 04/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/15/2026). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
By approaching the search of inurl:wp-admin/post.php it is possible to find vulnerable targets with Google Hacking.
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 EUVD (EUVD-2026-30513). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 3.28.0
- 3.28.1
- 3.28.2
- 3.28.3
- 3.28.4
- 3.28.5
- 3.28.6
- 3.28.7
- 3.28.8
- 3.28.9
- 3.28.10
- 3.28.11
- 3.28.12
- 3.28.13
- 3.28.14
- 3.28.15
- 3.28.16
- 3.28.17
- 3.28.18
- 3.28.19
- 3.28.20
- 3.28.21
- 3.28.22
- 3.28.23
- 3.28.24
- 3.28.25
- 3.28.26
- 3.28.27
- 3.28.28
- 3.28.29
- 3.28.30
- 3.28.31
- 3.28.32
- 3.28.33
- 3.28.34
- 3.28.35
- 3.28.36
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.8
CNA Vector (Wordfence): 🔒
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
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/13/2026 CVE reserved05/15/2026 Advisory disclosed
05/15/2026 VulDB entry created
05/15/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Colin Xu
Status: Not defined
CVE: CVE-2026-6228 (🔒)
GCVE (CVE): GCVE-0-2026-6228
GCVE (VulDB): GCVE-100-364151
EUVD: 🔒
Entry
Created: 05/15/2026 11:24Updated: 05/15/2026 12:46
Changes: 05/15/2026 11:24 (68), 05/15/2026 12:46 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.