CVE-2026-15158
Deferred Deferred - Pending Action

Arbitrary File Upload in Blocksy Companion WordPress Plugin

Vulnerability report for CVE-2026-15158, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-09

Last updated on: 2026-07-09

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-09
Last Modified
2026-07-09
Generated
2026-07-11
AI Q&A
2026-07-09
EPSS Evaluated
2026-07-09
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
blocksy companion to 2.1.46 (inc)
blocksy blocksy_companion_pro to 2.1.46 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-434 The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Blocksy Companion plugin for WordPress has a vulnerability in versions up to and including 2.1.46 that allows arbitrary file uploads. This happens because the Custom Fonts extension uses a filter that approves any filename containing '.woff2' or '.ttf' anywhere in the name, rather than ensuring these are the actual file extensions. As a result, files with double extensions like 'shell.woff2.php' can bypass MIME type validation and be treated as allowed font files.

This flaw enables unauthenticated attackers to upload potentially executable files, which can lead to remote code execution on the affected system.

Note that 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 version of the plugin does not contain this vulnerable code.

Impact Analysis

This vulnerability can have severe impacts because it allows unauthenticated attackers to upload arbitrary files that may be executable. This can lead to remote code execution, meaning attackers could run malicious code on your server.

Such an exploit could compromise the integrity, confidentiality, and availability of your website and server, potentially leading to data breaches, defacement, or full system takeover.

Mitigation Strategies

To mitigate this vulnerability, immediately update the Blocksy Companion plugin and its premium version (blocksy-companion-pro) to a version later than 2.1.46 where the issue is fixed.

If updating is not immediately possible, disable the premium version of the plugin or deactivate both the WooCommerce Extra (Advanced Reviews) and Custom Fonts extensions, as the vulnerability is only exploitable when these are active.

Additionally, restrict file upload permissions and monitor for any suspicious file uploads, especially files with double extensions like .woff2.php.

Detection Guidance

This vulnerability involves the ability to upload files with double extensions such as shell.woff2.php that bypass MIME validation. Detection can focus on identifying suspicious uploaded files with double extensions or unusual file types in the WordPress uploads directory or wherever the Blocksy Companion plugin stores attachments.

  • Search for files with suspicious double extensions like *.woff2.php or *.ttf.php in the uploads directory.
  • Check web server logs for HTTP POST requests to the save_attachments function or upload endpoints related to the Blocksy Companion plugin.
  • Use commands such as: find /path/to/wordpress/wp-content/uploads -type f -name '*.woff2.php' -o -name '*.ttf.php'
  • Review recently uploaded files for unexpected extensions or executable code.
Compliance Impact

The vulnerability allows unauthenticated attackers to upload potentially executable files, leading to remote code execution. This can result in unauthorized access, data breaches, or system compromise.

Such security breaches can impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.

Therefore, exploitation of this vulnerability could lead to violations of these regulations due to potential data exposure or loss of system integrity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15158. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart