CVE-2026-107645
CriticalCVSS 9.1Summary
The Blocksy Companion plugin up to version 2.1.58 is vulnerable to privilege escalation. The implement_user_registration() AJAX handler disables Dokan's vendor-registration nonce check and trusts an attacker-supplied $_POST['role'] value, allowing unauthenticated attackers to obtain a Dokan 'seller' account and be auto-authenticated, even when vendor signup is disabled.
Risk Assessment
An attacker can gain seller privileges, enabling content publishing and potentially leading to further abuse, including full site compromise.
Recommendation
Update the plugin to the latest patched version. If not available, temporarily disable user registration or apply additional security measures.
Other vulnerabilities in Blocksy Companion
See all- CVE-2026-97247Medium
Unauthenticated Broken Access Control vulnerability in Blocksy Companion versions up to 2.1.55.
- CVE-2026-15158Critical
The Blocksy Companion plugin for WordPress is vulnerable to arbitrary file upload in versions up to 2.1.46. The flaw lies in the save_attachments function, which improperly validates file extensions, allowing double-extension files like shell.woff2.php to bypass MIME checks. This can lead to remote code execution, but exploitation requires the premium plugin with specific extensions active.
- CVE-2026-18488Medium
The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tagName' block attribute in all versions up to and including 2.1.51. Authenticated attackers with author-level access or higher can inject arbitrary web scripts that execute whenever a user accesses an injected page.
- CVE-2025-12475Medium
The Blocksy Companion plugin for WordPress (up to 2.1.14) is vulnerable to Stored XSS via the 'blocksy_newsletter_subscribe' shortcode due to insufficient input sanitization and output escaping.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS