Skip to main content

Frontend Admin by DynamiApps CVE-2026-6228

| EUVDEUVD-2026-30513 HIGH
Improper Privilege Management (CWE-269)
2026-05-15 Wordfence GHSA-g3qj-jqcf-jg78
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Register editor account via public form
  2. Delivery
    Authenticate to WordPress backend
  3. Exploit
    Create edit_user form in plugin
  4. Install
    Intercept POST request to wp-admin/post.php
  5. C2
    Inject 'administrator' into role_options array
  6. Execute
    Save malicious form configuration
  7. Impact
    Access crafted form on frontend
  8. Step 8
    Submit own user ID with administrator role
  9. Step 9
    Bypass authorization check in pre_update_value()
  10. Step 10
    Escalate privileges to administrator

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
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

Exploitation requires three specific conditions to be met: (1) The WordPress site must have the Frontend Admin by DynamiApps plugin versions up to 3.28.36 installed and active. (2) The site must have public user registration enabled AND configured with a new_user form that grants editor-level privileges to newly registered accounts-this is NOT a default WordPress configuration and represents a specific deployment choice by site administrators. Sites with registration disabled or that assign only subscriber/contributor roles are not exploitable via the unauthenticated path. (3) The attacker must be able to create admin_form posts, which requires editor privileges due to the 'capability_type' => 'page' configuration. LIMITING FACTORS: Exploitation requires low privileges (editor account, PR:L) rather than unauthenticated access unless condition (2) is met. The vulnerability cannot be exploited by subscriber or contributor level accounts. Network access (AV:N) and no user interaction (UI:N) mean once an editor account is obtained, exploitation is straightforward. The attack complexity is low (AC:L) as it requires only basic HTTP request manipulation using browser developer tools or similar utilities. Sites following WordPress security best practices of limiting public registration roles and carefully vetting editor-level access have significantly reduced exposure.

Impact

Real-world risk is HIGH for installations with public user registration enabled. The CVSS vector (AV:N/AC:L/PR:L/UI:N) indicates network-accessible exploitation with low complexity requiring only low privileges (editor account), but this understates practical risk in certain deployment scenarios. Attack complexity is genuinely low: attackers need only (1) obtain editor access via public registration forms and (2) manipulate POST requests-both achievable with basic web debugging tools. The vulnerability enables complete site takeover through administrator privilege escalation, affecting confidentiality, integrity, and availability (C:H/I:H/A:H). No EPSS score or KEV status provided, suggesting exploitation is not yet widespread. However, the detailed technical disclosure including specific code references (class-role.php lines 107-110, post-types.php line 53) and patch changeset (3519460) provides a roadmap for exploit development. CRITICAL LIMITING FACTOR: Exploitation requires the site to have enabled public user registration AND configured new_user forms that grant editor role-not default WordPress behavior. Sites with registration disabled or that assign only subscriber/contributor roles to new users are NOT exploitable via the unauthenticated path described, though existing compromised editor accounts remain a risk vector. Administrators should immediately audit whether public registration grants editor privileges, as this significantly amplifies exploitability from opportunistic to remotely achievable by unauthenticated attackers.

Exploit ScenarioDerived

An attacker discovers a WordPress site running Frontend Admin by DynamiApps 3.28.36 with public registration enabled. They register a new account via a public new_user form configured to grant editor privileges. Authenticated as an editor, the attacker navigates to the form creation interface and begins creating an edit_user form. Using browser developer tools, they intercept the POST request to wp-admin/post.php and inject 'administrator' into the role_options array in the form configuration JSON, bypassing the UI restrictions in feadmin_get_user_roles(). After saving the malicious form, they access it via the frontend and submit their own user ID with the administrator role selected. The vulnerable pre_update_value() function validates only that 'administrator' exists in the form's allowed roles array without checking the attacker's authorization to assign that role, successfully escalating their account to administrator. The attacker now has complete control over the WordPress site, including the ability to install malicious plugins, modify content, access sensitive data, and create persistent backdoors.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 15, 2026

Privilege escalation in Frontend Admin by DynamiApps plugin allows authenticated attackers with editor-level access to elevate privileges to administrator. The vulnerability exists due to insufficient authorization checks when configuring user role options in edit_user forms combined with overly permissive capabilities on the admin_form post type. Attackers can bypass UI restrictions by directly manipulating POST data to include 'administrator' in role_options, then use the crafted form to assign themselves administrator privileges. CVSS 8.8 reflects network-accessible, low-complexity exploitation requiring only low privileges (editor account). No public exploit code identified at time of analysis, though the attack chain is straightforward for authenticated users. EPSS data not provided, but the technical barrier is minimal once editor access is obtained.

RemediationAI

Immediately update Frontend Admin by DynamiApps to version 3.28.37 or later, which addresses the privilege escalation vulnerability per changeset 3519460 documented at https://plugins.trac.wordpress.org/changeset/3519460. The patch implements proper authorization checks in the role assignment mechanism to verify that users have sufficient privileges before allowing role escalation. Until patching is complete, implement these compensating controls: (1) Disable public user registration in WordPress (Settings → General → Membership: uncheck 'Anyone can register') to prevent the unauthenticated attack path-this eliminates the most severe exploitation scenario but does not address risk from existing compromised editor accounts. (2) If registration must remain enabled, configure new_user forms to assign only subscriber or contributor roles, never editor or above-this breaks the initial access requirement in the attack chain. (3) Audit existing user accounts for unexpected privilege escalations by reviewing Users list for recently created administrator accounts and checking admin activity logs if available. (4) Restrict editor access to the admin_form post type by implementing custom capability filters, though this requires code modification and may break legitimate plugin functionality. Note that workarounds (1) and (2) prevent new exploitation but do not remove the underlying vulnerability-patching remains the definitive solution.

Affected VersionsENISA

Frontend Admin by DynamiApps 0 ≤3.28.36

Affected Packages

euvd frontend_admin_by_dynamiapps no fix

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

This vulnerability affects the Frontend Admin by DynamiApps WordPress plugin (CPE: cpe:2.3:a:shabti:frontend_admin_by_dynamiapps), specifically its role assignment mechanism in user management forms. The root cause (CWE-269: Improper Privilege Management) stems from two architectural flaws: (1) The admin_form custom post type uses 'capability_type' => 'page', which grants WordPress editors the edit_pages capability, allowing them to create and modify admin forms. (2) The pre_update_value() function in class-role.php validates only that the submitted role exists in the form's role_options array but fails to verify whether the current user has sufficient privileges to assign that specific role. The plugin's feadmin_get_user_roles() UI function filters available roles, but this client-side restriction is bypassed when attackers directly POST data to wp-admin/post.php. WordPress's built-in role hierarchy (subscriber < contributor < author < editor < administrator) should prevent lower-privileged users from assigning higher roles, but the plugin's custom form handling bypasses these native protections.

Know when Frontend Admin By Dynamiapps 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

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The Frontend Admin by DynamiApps plugin contains a privilege escalation vulnerability (CVE-2026-6228) that allows authenticated editors to gain administrator access by manipulating form data, directly compromising administrative control of affected WordPress sites. Organizations using this plugin face immediate risk of unauthorized administrative takeover if editor accounts are compromised or if editor-level users act maliciously, with no vendor patch currently available to remediate the flaw.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable the Frontend Admin by DynamiApps plugin until a patched version is released; (2) Restrict editor-level user accounts to trusted personnel only and implement principle of least privilege; (3) Enable WordPress security logging and monitor for unauthorized role assignment changes; (4) Use Web Application Firewall (WAF) rules to detect POST requests containing 'administrator' role parameters in edit_user forms; (5) Regularly audit user capabilities and role assignments.

Threat Intelligence Overview

EPSS Score
0.1%
Top 71% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2026-13609 HIGH POC
8.8 Jul 31

Stored cross-site scripting in the Frontend Admin by DynamiApps WordPress plugin (all versions before 3.29.9) allows una

CVE-2026-11867 MEDIUM POC
6.5 Jul 30

Missing authorization in Frontend Admin by DynamiApps WordPress plugin (versions before 3.29.7) exposes taxonomy term cr

CVE-2026-81347 MEDIUM POC
5.9 Sep 04

Unauthenticated path traversal file deletion in the Frontend Admin by DynamiApps WordPress plugin before 3.29.13 allows

CVE-2026-75816 CRITICAL
9.8 Sep 06

Unauthenticated account takeover in the Frontend Admin by DynamiApps WordPress plugin (all versions through 3.29.12) let

CVE-2026-18432 CRITICAL
9.8 Aug 16

Privilege escalation in the Frontend Admin by DynamiApps WordPress plugin (all versions through 3.29.9) lets attackers t

CVE-2026-66662 CRITICAL
9.8 Aug 06

Privilege escalation in the Frontend Admin by DynamiApps WordPress plugin (versions up to and including 3.29.10) lets re

CVE-2026-15606 HIGH
8.8 Aug 11

Password reset authorization bypass in the Frontend Admin by DynamiApps WordPress plugin (all versions through 3.29.9) a

CVE-2026-6226 HIGH
8.8 May 28

Unauthenticated privilege escalation in the Frontend Admin by DynamiApps WordPress plugin (versions up to and including

CVE-2026-7802 HIGH
8.8 May 28

Privilege escalation in the Frontend Admin by DynamiApps WordPress plugin (versions up to and including 3.29.2) allows a

CVE-2026-81346 MEDIUM POC
4.3 Aug 29

Unauthorized deletion of arbitrary membership plans is possible in the Frontend Admin by DynamiApps WordPress plugin (al

CVE-2026-19952 HIGH
7.5 Sep 01

Unauthenticated arbitrary file deletion in the Frontend Admin by DynamiApps WordPress plugin (versions up to and includi

CVE-2026-42722 HIGH
7.6 Oct 10

SQL injection in the Frontend Admin by DynamiApps WordPress plugin (all versions up to and including 3.29.13) lets an au

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy