Blocksy Companion <= 2.1.58 - Unauthenticated Privilege Escalation to 'role' Parameter
Strategic Overview
- Status
- Patched in 2.1.59
- Affected Plugin
- Blocksy Companion
- Affected Version
<= 2.1.58- CVSS
- 9.1Critical
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-107645
At a glance
CVE-2026-107645 is a critical-severity Improper Privilege Management vulnerability in the Blocksy Companion WordPress plugin, affecting versions <= 2.1.58. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.1.59; sites on affected versions should update now. Disclosed October 2026, reported by Sawyer.
Vulnerability Overview
The Blocksy Companion plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 2.1.58 This is due to the implement_user_registration() AJAX handler explicitly disabling Dokan's vendor-registration nonce check (via add_filter('dokan_register_nonce_check', '__return_false')) and then trusting an attacker-supplied $_POST['role'] value when invoking wc_create_new_customer() and wc_set_customer_auth_cookie(). This makes it possible for unauthenticated attackers to elevate their privileges to a Dokan 'seller' (vendor) account — including sites where the Dokan vendor signup is explicitly turned off — and to be auto-authenticated into that account, which grants publishing capabilities beyond those of a normal customer.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity.
CWE-269: Improper Privilege Management
Blocksy Companion <= 2.1.58 carries this weakness at dokan_register_nonce_check, and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Blocksy Companion the fix is 2.1.59: builds <= 2.1.58 are affected, anything from 2.1.59 onward is not.
Remediation
Update to version 2.1.59, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Blocksy Companion 2.1.59 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Blocksy Companion
- 9.8CVE-2026-15158: Blocksy Companion <= 2.1.46 Arbitrary File Upload
CVE-2026-15158 - 8.8CVE-2025-12846: Blocksy Companion <= 2.1.19 Arbitrary File Upload
CVE-2025-12846 - 6.4CVE-2026-18488: Blocksy Companion <= 2.1.51 Stored XSS
CVE-2026-18488 - 6.4CVE-2025-12475: Blocksy Companion <= 2.1.14 Stored XSS
CVE-2025-12475 - 6.4CVE-2025-9565: Blocksy Companion <= 2.1.10 Stored Cross-Site Scripting
CVE-2025-9565 - 6.4CVE-2024-4487: Blocksy Companion <= 2.0.45 Stored Cross-Site Scripting
CVE-2024-4487 - 6.4CVE-2024-2392: Blocksy Companion <= 2.0.31 Stored Cross-Site Scripting
CVE-2024-2392 - 6.4CVE-2023-23898: Blocksy Companion <= 1.8.67 Stored XSS
CVE-2023-23898
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C