Blocksy Companion at a glance
- 16 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
- Ranked #160 by popularity on WordPress.org (300,000+ active installs).
- The latest version is 2.1.62 (released Nov 12, 2026). The most recent security fix shipped in 2.1.61.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Blocksy Companion version
Enter the Blocksy Companion version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Blocksy Companion”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Blocksy Companion”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.1.62). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Blocksy Companion vulnerabilities
Blocksy Companion <= 2.1.60 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-65444
Affected versions: ≤ 2.1.60
Fixed in: 2.1.61
Severity: Medium 6.4 · Disclosed Oct 30, 2026
Blocksy Companion <= 2.1.58 - Unauthenticated Privilege Escalation to 'role' Parameter
Privilege escalation · CVE-2026-107645
Affected versions: ≤ 2.1.58
Fixed in: 2.1.59
Severity: Critical 9.1 · Disclosed Oct 9, 2026
Blocksy Companion <= 2.1.55 - Missing Authorization
Missing authorization · CVE-2026-97247
Affected versions: ≤ 2.1.55
Fixed in: 2.1.56
Severity: Medium 5.3 · Disclosed Sep 24, 2026
Blocksy Companion <= 2.1.51 - Authenticated (Author+) Stored Cross-Site Scripting via 'tagName' Block Attribute (blocksy/dynamic-data)
Cross-site scripting (XSS) · CVE-2026-18488
Affected versions: ≤ 2.1.51
Fixed in: 2.1.52
Severity: Medium 6.4 · Disclosed Aug 31, 2026
Blocksy Companion <= 2.1.46 - Unauthenticated Arbitrary File Upload via 'blc-review-images[]' Parameter
Arbitrary file upload · CVE-2026-15158
Affected versions: ≤ 2.1.46
Fixed in: 2.1.47
Severity: Critical 9.8 · Disclosed Jul 1, 2026
Blocksy Companion <= 2.1.45 - Authenticated (Editor+) Stored Cross-Site Scripting via 'product_description' Parameter
Cross-site scripting (XSS) · CVE-2026-12430
Affected versions: ≤ 2.1.45
Fixed in: 2.1.46
Severity: Medium 4.4 · Disclosed Jun 18, 2026
Blocksy Companion <= 2.1.19 - Authenticated (Author+) Arbitrary File Upload via SVG Upload Bypass
Arbitrary file upload · CVE-2025-12846
Affected versions: ≤ 2.1.19
Fixed in: 2.1.20
Severity: High 8.8 · Disclosed Nov 10, 2025
Blocksy Companion <= 2.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-12475
Affected versions: ≤ 2.1.14
Fixed in: 2.1.15
Severity: Medium 6.4 · Disclosed Oct 6, 2025
Blocksy Companion <= 2.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via blocksy_newsletter_subscribe Shortcode
Cross-site scripting (XSS) · CVE-2025-9565
Affected versions: ≤ 2.1.10
Fixed in: 2.1.11
Severity: Medium 6.4 · Disclosed Sep 16, 2025
Blocksy Companion <= 2.0.42 - Authenticated (Admin+) Server-Side Request Forgery
Server-side request forgery (SSRF) · CVE-2024-35633
Affected versions: ≤ 2.0.42
Fixed in: 2.0.43
Severity: Medium 5.5 · Disclosed May 30, 2024
Blocksy Companion <= 2.0.45 - Authenticated (Contributor+) Stored Cross-Site Scripting via SVG Uploads
Cross-site scripting (XSS) · CVE-2024-4487
Affected versions: ≤ 2.0.45
Fixed in: 2.0.46
Severity: Medium 6.4 · Disclosed May 10, 2024
Blocksy Companion <= 2.0.28 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2024-31932
Affected versions: ≤ 2.0.28
Fixed in: 2.0.29
Severity: Medium 5.3 · Disclosed Apr 10, 2024
Blocksy Companion <= 2.0.31 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-2392
Affected versions: ≤ 2.0.31
Fixed in: 2.0.32
Severity: Medium 6.4 · Disclosed Mar 21, 2024
Blocksy Companion <= 1.8.81 - Authenticated(Subscriber+) Sensitive Information Exposure via blocksy_posts shortcode
Missing authorization · CVE-2023-1911
Affected versions: ≤ 1.8.81
Fixed in: 1.8.82
Severity: Medium 4.3 · Disclosed Apr 10, 2023
Blocksy Companion <= 1.8.67 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-23898
Affected versions: < 1.8.68
Fixed in: 1.8.68
Severity: Medium 6.4 · Disclosed Jan 27, 2023
Freemius SDK <= 2.4.2 - Missing Authorization Checks
Missing authorization · CVE-2022-4974
Affected versions: < 1.8.20
Fixed in: 1.8.20
Severity: Medium 6.3 · Disclosed Mar 4, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Blocksy Companion <= 2.1.60 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-65444 | ≤ 2.1.60 | 2.1.61 | Medium 6.4 | Oct 30, 2026 |
| Blocksy Companion <= 2.1.58 - Unauthenticated Privilege Escalation to 'role' ParameterPrivilege escalation · CVE-2026-107645 | ≤ 2.1.58 | 2.1.59 | Critical 9.1 | Oct 9, 2026 |
| Blocksy Companion <= 2.1.55 - Missing AuthorizationMissing authorization · CVE-2026-97247 | ≤ 2.1.55 | 2.1.56 | Medium 5.3 | Sep 24, 2026 |
| Blocksy Companion <= 2.1.51 - Authenticated (Author+) Stored Cross-Site Scripting via 'tagName' Block Attribute (blocksy/dynamic-data)Cross-site scripting (XSS) · CVE-2026-18488 | ≤ 2.1.51 | 2.1.52 | Medium 6.4 | Aug 31, 2026 |
| Blocksy Companion <= 2.1.46 - Unauthenticated Arbitrary File Upload via 'blc-review-images[]' ParameterArbitrary file upload · CVE-2026-15158 | ≤ 2.1.46 | 2.1.47 | Critical 9.8 | Jul 1, 2026 |
| Blocksy Companion <= 2.1.45 - Authenticated (Editor+) Stored Cross-Site Scripting via 'product_description' ParameterCross-site scripting (XSS) · CVE-2026-12430 | ≤ 2.1.45 | 2.1.46 | Medium 4.4 | Jun 18, 2026 |
| Blocksy Companion <= 2.1.19 - Authenticated (Author+) Arbitrary File Upload via SVG Upload BypassArbitrary file upload · CVE-2025-12846 | ≤ 2.1.19 | 2.1.20 | High 8.8 | Nov 10, 2025 |
| Blocksy Companion <= 2.1.14 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-12475 | ≤ 2.1.14 | 2.1.15 | Medium 6.4 | Oct 6, 2025 |
| Blocksy Companion <= 2.1.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via blocksy_newsletter_subscribe ShortcodeCross-site scripting (XSS) · CVE-2025-9565 | ≤ 2.1.10 | 2.1.11 | Medium 6.4 | Sep 16, 2025 |
| Blocksy Companion <= 2.0.42 - Authenticated (Admin+) Server-Side Request ForgeryServer-side request forgery (SSRF) · CVE-2024-35633 | ≤ 2.0.42 | 2.0.43 | Medium 5.5 | May 30, 2024 |
| Blocksy Companion <= 2.0.45 - Authenticated (Contributor+) Stored Cross-Site Scripting via SVG UploadsCross-site scripting (XSS) · CVE-2024-4487 | ≤ 2.0.45 | 2.0.46 | Medium 6.4 | May 10, 2024 |
| Blocksy Companion <= 2.0.28 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2024-31932 | ≤ 2.0.28 | 2.0.29 | Medium 5.3 | Apr 10, 2024 |
| Blocksy Companion <= 2.0.31 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-2392 | ≤ 2.0.31 | 2.0.32 | Medium 6.4 | Mar 21, 2024 |
| Blocksy Companion <= 1.8.81 - Authenticated(Subscriber+) Sensitive Information Exposure via blocksy_posts shortcodeMissing authorization · CVE-2023-1911 | ≤ 1.8.81 | 1.8.82 | Medium 4.3 | Apr 10, 2023 |
| Blocksy Companion <= 1.8.67 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-23898 | < 1.8.68 | 1.8.68 | Medium 6.4 | Jan 27, 2023 |
| Freemius SDK <= 2.4.2 - Missing Authorization ChecksMissing authorization · CVE-2022-4974 | < 1.8.20 | 1.8.20 | Medium 6.3 | Mar 4, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.
Most common weaknesses in Blocksy Companion
Cross-site scripting (XSS)
8 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Arbitrary file upload
2 issues
An attacker can upload a malicious file disguised as an image or document. Once it is on the server, it can be used to take over the site.
Frequently asked questions
Is Blocksy Companion safe to use?
Blocksy Companion is a well-known plugin with 300,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.1.62) and turn on automatic updates.
How do I find which version of Blocksy Companion my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesBlocksy Companion on WordPress.org