Blocksy Companion Vulnerability: Update Now
If your site runs the Blocksy Companion plugin version 2.1.58 or older, update it to the latest version today, because a critical flaw (CVE-2026-107645) lets an anonymous visitor turn themselves into a Dokan vendor account.
This post is for owners of WordPress and WooCommerce sites that use the Blocksy theme, and especially for anyone running a Dokan marketplace. You will learn what the bug is in plain English, how to check your version, how to update safely, and how to look for suspicious accounts afterward.
What happened, in plain English
Blocksy is a popular WordPress theme. Blocksy Companion is the plugin that adds extra features to it, including a login and registration pop-up. The bug lives in that plugin's account code, not in the theme files themselves.
The National Vulnerability Database (NVD) entry for CVE-2026-107645 was published on 2026-10-10. It says the registration handler in Blocksy Companion versions up to and including 2.1.58 can be tricked into giving a new account a higher role than it should have.
This kind of bug is called privilege escalation. That means a person gets more power on your site than you meant to give them. It is a form of what OWASP calls broken access control, and the weakness is filed as CWE-269 (improper privilege management).
How the flaw works
Dokan is a plugin that turns WooCommerce into a marketplace with many sellers. Each seller gets a "vendor" account that can add and publish products.
According to the NVD description, two things went wrong in the Blocksy Companion sign-up code:
- The code switched off Dokan's built-in security check for vendor registration. That check is called a nonce, a one-time token that proves a form request came from a real page on your site.
- The code then trusted a "role" value sent by the visitor. It used that value to create the account and log the person in right away.
Put together, an unauthenticated visitor (someone with no account at all) can ask for a Dokan "seller" account and get one, already logged in. The NVD says this works even on sites where Dokan vendor sign-up is turned off. Seller accounts can publish content, which goes beyond what a normal customer can do.
I am not going to describe how to send such a request. You do not need that to protect your site.
How serious is it?
The NVD record lists a CVSS score of 9.1 out of 10, rated Critical. CVSS is a standard scoring system for vulnerability severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Here is what the main parts mean:
| Part | Value | What it means for you |
|---|---|---|
| AV:N | Network | Can be attempted over the internet |
| AC:L | Low complexity | No special conditions needed |
| PR:N | No privileges | The visitor does not need an account |
| UI:N | No user interaction | You or your staff do not have to click anything |
| C:H / I:H | High | Large impact on data exposure and data changes |
| A:N | None | The score does not count the site going offline |
The NVD status is currently "Deferred". That means NVD has marked the record for deferred analysis, so it has not been fully enriched yet. It does not make the issue less real. The record also does not list affected versions separately, so the "2.1.58 and older" range comes from the description text.
The sources I reviewed do not say whether anyone is actively using this bug against real sites. Treat that as unknown, not as safe.
Are you affected?
Use this quick table to decide how urgent this is.
| Your situation | Risk | What to do |
|---|---|---|
| Blocksy Companion 2.1.58 or older and Dokan installed | Highest. This is the exact path in the description | Update now, then audit seller accounts |
| Blocksy Companion 2.1.58 or older, no Dokan | The published description only covers Dokan seller accounts, and we have not seen the impact without Dokan described | Update anyway, and review your user list |
| Blocksy Companion newer than 2.1.58 | The fix appears in a later release (see below) | Keep updating, and still check your user list |
| Blocksy theme only, no Companion plugin | The flaw is in the plugin | Nothing to patch for this CVE |
If you are not sure whether Dokan is on your site, go to Plugins > Installed Plugins in your WordPress dashboard and look for "Dokan". Also check whether your site has a "Vendors" or "Sellers" area.
Step 1: Check your Blocksy Companion version
In the dashboard, open Plugins > Installed Plugins and find "Blocksy Companion". The version number is shown under its name.
If you have command-line access with WP-CLI (the official WordPress command-line tool), you can run:
wp plugin get blocksy-companion --field=version
If the result is 2.1.58 or lower, you are in the affected range.
Step 2: Back up, then update
Take a backup first. Most hosts offer one-click backups. With WP-CLI you can export the database like this:
wp db export ~/before-blocksy-update.sql
Run this from your WordPress folder, but save the file outside the public web root (or delete it afterwards), because a .sql file inside the site folder can be downloaded by anyone who guesses its URL, and it holds password hashes.
Then update from the dashboard (Plugins > Installed Plugins > Update now under Blocksy Companion), or with WP-CLI:
wp plugin update blocksy-companion
The NVD references include a WordPress.org code changeset for version 2.1.59 that touches the same account file, which points to 2.1.59 as the release that addressed it. The NVD record itself does not name a fixed version, so the safe move is to install the latest version and read the changelog on the Blocksy Companion plugin page to confirm. There is also a write-up from Wordfence's vulnerability database if you want a second source.
After updating, load your login page, registration pop-up and checkout in a private browser window. Make sure they still work.
Step 3: Look for accounts you did not expect
Updating closes the door. It does not tell you whether someone already walked through. If your site was on 2.1.58 or older for any length of time, take ten minutes to check.
- Go to Users > All Users in WordPress.
- Sort by registration date or look at the newest accounts. Look for names or emails you do not recognize.
- On a Dokan site, filter by the Vendor or Seller role and confirm each one is a real seller you approved.
With WP-CLI, this lists seller accounts with their sign-up dates (Dokan's role is named seller):
wp user list --role=seller --fields=ID,user_login,user_email,user_registered
If you find an account you do not recognize:
- Do not just delete it yet. Note the username, email and date so you have a record.
- Check what that account published. Look at Products, Posts and Pages for anything you did not add, such as odd links or spammy listings.
- Remove the content you did not authorize, then remove the account or reset its role to something harmless.
- Change the passwords of your administrator accounts as a precaution.
If you see signs of a wider break-in, such as admin users you did not create or files you do not recognize, follow our hacked website checklist.
Why updating is better than a workaround
You may be tempted to hide the sign-up pop-up or close registration as a quick fix. Do not rely on that. The NVD description says the flaw sits in an AJAX handler (a background request your site answers without loading a full page), so hiding a button on the page may not close it. I cannot confirm any workaround is complete, so patching is the answer.
If you cannot update today, deactivating Blocksy Companion removes the vulnerable handler. Your theme's look and login pop-up may change, so check the site right after, and update as soon as you can.
Keep this from catching you off guard next time
This is a common pattern for WordPress: the platform itself is fine, but a plugin has a bug, and sites that lag on updates are the ones exposed. A few habits help a lot:
- Turn on automatic updates for plugins you trust. In the dashboard, go to Plugins > Installed Plugins and click Enable auto-updates next to each one.
- Remove plugins you no longer use. Fewer plugins means fewer places for bugs to hide.
- Limit who can register. If your site does not need public accounts, turn them off under Settings > General by unchecking Anyone can register. This is general hygiene only. It does not protect against CVE-2026-107645, so update the plugin regardless.
- Make sure you have working backups that you have actually tested.
An easy first step is our free website security check, which looks at your site from the outside. If you want to understand your wider risk, see our guide on whether your website is hackable.
Key takeaways
- Update Blocksy Companion to the latest version now. Versions up to and including 2.1.58 are described as vulnerable in CVE-2026-107645.
- The flaw lets an unauthenticated visitor get a Dokan seller account and be logged in automatically, even if vendor sign-up is off, according to the NVD.
- The score is CVSS 9.1 (Critical). Patching beats any workaround.
- After updating, review your user list and any seller accounts, and check for content you did not publish.
- Check the plugin changelog to confirm the fixed version, since the NVD record does not list one.
Want a human to look at your site?
A patch fixes one bug. A person reviewing your whole site can find the others. Our Circuit audit is a $49 one-time manual review of a small site, with a written report that lists each issue, its severity, the evidence and the exact fix. It is a focused small-site audit, not an enterprise penetration test or a compliance certificate. If you would rather have us fix the serious problems for you, the plans on the same page cover that too.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing