Atomic Edge analysis of CVE-2026-66665 (metadata-based): The Type Hub plugin for WordPress (up to 2.0.6) contains an unauthenticated arbitrary file upload vulnerability. Missing file type validation in an upload handler allows unauthenticated attackers to upload dangerous files, potentially leading to remote code execution (RCE). The CVSS score is 9.8 (Critical) with a vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, reflecting network exploitability, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability.
Root Cause: Based on CWE-434 (Unrestricted Upload of File with Dangerous Type) and the description, the root cause is the absence of file type validation in an upload routine. Atomic Edge analysis infers that the plugin registers an AJAX action (likely via wp_ajax_nopriv_ or a REST endpoint) that accepts file uploads without checking the file extension, MIME type, or content. Without a code diff, the exact vulnerable function cannot be confirmed, but the missing validation is confirmed by the CWE and description. The vulnerability is unauthenticated, so the handler lacks capability checks or nonce verification.
Exploitation: Attackers send a POST request to /wp-admin/admin-ajax.php with an action parameter matching the plugin’s upload handler (e.g., action=typehub_upload or similar). The request includes a file upload via multipart/form-data. Because the handler lacks file type validation, an attacker can upload a .php file containing malicious code. The file is likely stored in an upload directory (e.g., /wp-content/uploads/). Atomic Edge research indicates that the exact action name and parameter names are inferred from the plugin slug and common WordPress patterns, as no source code is available. Attackers may need to guess or discover the action name, but the high CVSS score suggests it is easily identifiable.
Remediation: The fix requires adding proper file type validation in the upload handler. This includes checking the file extension against an allowlist, validating the MIME type, and ensuring the file content matches the expected type. The handler should also enforce capability checks and nonce verification for authenticated users, but since the vulnerability is unauthenticated, the primary fix is to restrict uploads to authenticated users with proper permissions or to remove the unauthenticated upload functionality entirely. Atomic Edge analysis suggests that the lack of a patched version (none available) means site owners should disable or remove the plugin.
Impact: Successful exploitation allows an attacker to upload and execute arbitrary PHP code, leading to full remote code execution. This can result in complete compromise of the WordPress site, including data theft, malware injection, privilege escalation, and use of the server for further attacks. The high CVSS score reflects the severity: unauthenticated attackers can achieve complete system compromise.







