Reported vulnerability

Blocksy Companion <= 2.1.46 - Unauthenticated Arbitrary File Upload via 'blc-review-images[]' Parameter

Q: Which versions of Blocksy Companion are affected?

Wordfence lists these affected versions: Start version unspecified, through 2.1.46. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for Blocksy Companion?

Wordfence reports a fix for this issue in Blocksy Companion. It lists these fixed versions: 2.1.47. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed plugin version?

In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.

Published 1 Jul 2026

Updated 9 Jul 2026

CVE-2026-15158

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

critical · CVSS 9.8

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. CVE-2026-58480 is a duplicate of this CVE.

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Blocksy Companion

Software: plugin · blocksy-companion
Affected versions: Start version unspecified, through 2.1.46
Fix availability: Fix available
Fixed versions: 2.1.47

Recommended action

Update to version 2.1.47, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/2df449b4-3f3b-4afc-b391-8d8d11710c07?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of Blocksy Companion are affected?

Wordfence lists these affected versions: Start version unspecified, through 2.1.46. Use the version checker above to compare your installed release with this report.

Is a fix available for Blocksy Companion?

Wordfence reports a fix for this issue in Blocksy Companion. It lists these fixed versions: 2.1.47. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed plugin version?

In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database