Critical Vulnerability in Blocksy Companion Pro for WordPress
An early warning has been issued regarding a critical vulnerability in the Blocksy Companion Pro plugin for WordPress, versions prior to 2.1.47. This vulnerability, reportedly tracked as CVE-2026-15158 and CVE-2026-58480, allows for unauthenticated arbitrary file uploads, potentially enabling remote code execution.
What happened
The Blocksy Companion Pro plugin for WordPress, in versions before 2.1.47, reportedly contains a critical vulnerability that permits unauthenticated arbitrary file uploads. This vulnerability, under investigation and tracked as CVE-2026-15158 and CVE-2026-58480, allows attackers to bypass extension validation by uploading files with double extensions, such as shell.woff2.php. This can lead to remote code execution if the uploaded file is executable. The vulnerability is reportedly exploitable when the premium version of the plugin is installed with both the WooCommerce Extra (Advanced Reviews) and Custom Fonts extensions active.
To assess your exposure, verify if your WordPress installation utilizes the Blocksy Companion Pro plugin, particularly with the WooCommerce Extra and Custom Fonts extensions enabled. If so, it is recommended to upgrade to version 2.1.47 or later to mitigate the risk of remote code execution. For more detailed information, consult the primary sources provided by the National Vulnerability Database (NVD).
How 0Day mitigates this
blocksy-companion-pro is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.