CyberRota Analysis
AI-GeneratedThe Blocksy Companion plugin for WordPress is vulnerable to arbitrary file uploads, allowing unauthenticated attackers to upload potentially executable files due to improper validation of file extensions in the save_attachments function. This critical vulnerability can lead to remote code execution when the premium version of the plugin is used alongside specific extensions, making it imperative for users of the premium Blocksy Companion plugin, especially those with WooCommerce Extra and Custom Fonts extensions enabled, to prioritize immediate remediation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The Blocksy Companion plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.1.46 via the save_attachments function. This is due to the Custom Fonts extension registering a wp_check_filetype_and_ext filter that approves any filename containing .woff2 or .ttf as a substring via strpos() rather than validating that those strings appear as the final extension via PATHINFO_EXTENSION — allowing double-extension filenames such as shell.woff2.php to pass MIME validation and be handled as permitted font files. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. This vulnerability is only exploitable when the premium version of the plugin (blocksy-companion-pro) is installed with both the WooCommerce Extra (Advanced Reviews) and Custom Fonts extensions active; the free blocksy-companion plugin does not contain the vulnerable code paths.