HomeWordPress vulnerabilitiesBlocksy Companion
Blocksy Companion vulnerabilities
Blocksy Companion has 10 known vulnerabilities in this database. The most recent published record is dated 1 Sep 2026.
- Known vulnerabilities
- 10
- Active installs
- 300,000+
- Latest version
- 2.1.57
- Last updated
- 10 Sep 2026
- Most recent
- 1 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-18488 | Medium 6.4 | Up to 2.1.51 | Fixed in a later version (latest 2.1.57) | 1 Sep 2026 |
| Remote code execution CVE-2026-15158 | Critical 9.8 | Up to 2.1.46 | Fixed in a later version (latest 2.1.57) | 9 Jul 2026 |
| Remote code execution CVE-2026-58480 | Critical 9.8 | Before 2.1.47 | Fixed in 2.1.47 | 8 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-12430 | Medium 4.4 | Up to 2.1.45 | Fixed in a later version (latest 2.1.57) | 19 Jun 2026 |
| Remote code execution CVE-2025-12846 | High 8.8 | Up to 2.1.19 | Fixed in a later version (latest 2.1.57) | 11 Nov 2025 |
| Cross-site scripting (XSS) CVE-2025-12475 | Medium 6.4 | Up to 2.1.14 | Fixed in a later version (latest 2.1.57) | 30 Oct 2025 |
| Cross-site scripting (XSS) CVE-2025-9565 | Medium 6.4 | Up to 2.1.10 | Fixed in a later version (latest 2.1.57) | 17 Sep 2025 |
| Cross-site scripting (XSS) CVE-2024-4487 | Medium 6.4 | Before 2.0.46 | Fixed in 2.0.46 | 14 May 2024 |
| Cross-site scripting (XSS) CVE-2024-2392 | Medium 6.4 | Before 2.0.32 | Fixed in 2.0.32 | 22 Mar 2024 |
| Broken access control CVE-2023-1911 | Medium 4.3 | Before 1.8.82 | Fixed in 1.8.82 | 2 May 2023 |
Read the published descriptions
- CVE-2026-18488, 1 Sep 2026
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'tagName' Block Attribute (blocksy/dynamic-data) in all versions up to, and including, 2.1.51 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-15158, 9 Jul 2026
- 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 record
- CVE-2026-58480, 8 Jul 2026
- Blocksy Companion Pro plugin for WordPress before 2.1.47 contains an unauthenticated arbitrary file upload vulnerability that allows attackers to upload executable files by bypassing extension validation in the save_attachments function exposed through the Advanced Reviews feature. Attackers can exploit the Custom Fonts extension's flawed strpos() substring check by uploading double-extension filenames such as shell.woff2.php, causing the validation to pass on the substring match while the web server executes the file as PHP, achieving remote code execution. CVE record
- CVE-2026-12430, 19 Jun 2026
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.1.45 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
- CVE-2025-12846, 11 Nov 2025
- The Blocksy Companion plugin for WordPress is vulnerable to authenticated arbitrary file upload in all versions up to, and including, 2.1.19. This is due to insufficient file type validation detecting SVG files, allowing double extension files to bypass sanitization while being accepted as a valid SVG file. This makes it possible for authenticated attackers, with author level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2025-12475, 30 Oct 2025
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'blocksy_newsletter_subscribe' shortcode in all versions up to, and including, 2.1.14 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-9565, 17 Sep 2025
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's blocksy_newsletter_subscribe shortcode in all versions up to, and including, 2.1.10 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-4487, 14 May 2024
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG uploads in versions up to, and including, 2.0.45 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-2392, 22 Mar 2024
- The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Newsletter widget in all versions up to, and including, 2.0.31 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-1911, 2 May 2023
- The Blocksy Companion WordPress plugin before 1.8.82 does not ensure that posts to be accessed via a shortcode are already public and can be viewed, allowing any authenticated users, such as subscriber to access draft posts for example CVE record
What to do if you run Blocksy Companion
If you run Blocksy Companion, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Blocksy Companion vulnerabilities
Free. We email you when a new vulnerability is published for Blocksy Companion, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.