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.
Published: 2026-07-09
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Blocksy Companion plugin for WordPress contains an arbitrary file upload flaw that allows an unauthenticated attacker to upload a file with a double extension, such as shell.woff2.php, through the 'blc-review-images[]' parameter. The flaw stems from a custom validation filter that incorrectly accepts any filename containing ".woff2" or ".ttf" as a substring, rather than verifying the actual file extension. This permits files that are executable on the server to be stored as seemingly harmless font files, enabling remote code execution if the server is configured to execute the uploaded file type. The weakness is categorized as "Arbitrary File Upload" (CWE-434).

Affected Systems

Blocksy Companion, developed by creativethemeshq, is affected in all releases up to and including version 2.1.46. The flaw is only exploitable when the premium blocksy‑companion‑pro version is installed together with both the WooCommerce Extra (Advanced Reviews) and Custom Fonts extensions. Installations of the free blocksy‑companion plugin are not vulnerable because the vulnerable code paths are absent.

Risk and Exploitability

The vulnerability carries a CVSS score of 9.8, indicating critical severity. Its EPSS score is less than 1%, suggesting that exploitation opportunities are currently rare, and the flaw is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector is the unauthenticated upload endpoint exposed by the plugin; an attacker can send a crafted request containing a malicious file name that passes on the server, and then trigger server’s file handling rules.

Generated by OpenCVE AI on July 28, 2026 at 08:53 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Blocksy Companion update (any version newer than 2.1.46).
  • If an update is not yet available, remove or disable the Custom Fonts and Advanced Reviews extensions from the premium plugin until the issue is patched.
  • Delete any files that have been uploaded via the plugin’s attachment feature that contain unexpected extensions or suspicious names, and ensure the web server blocks execution of uploaded files through appropriate configuration such as a .htaccess rule or server‑side restrictions.

Generated by OpenCVE AI on July 28, 2026 at 08:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 09 Jul 2026 09:30:00 +0000

Type Values Removed Values Added
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.
Title Blocksy Companion <= 2.1.46 - Unauthenticated Arbitrary File Upload via 'blc-review-images[]' Parameter
Weaknesses CWE-434
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-07-09T13:52:43.210Z

Reserved: 2026-07-08T20:08:13.444Z

Link: CVE-2026-15158

cve-icon Vulnrichment

Updated: 2026-07-09T13:52:37.238Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-28T09:00:06Z

Weaknesses
  • CWE-434

    Unrestricted Upload of File with Dangerous Type