Read the docs

Unauthenticated privilege escalation in Blocksy Companion

Priority MEDIUM 47CWE-269Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Privilege escalation
Confidentiality · integrity · availability
High · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-269.

Summary

The Blocksy Companion plugin for WordPress is affected through version 2.1.58. An AJAX registration handler trusts a user-supplied role value, which is improper privilege management (CWE-269). An unauthenticated remote attacker can register as a Dokan seller account, even where vendor signup is disabled, and the handler logs the attacker in automatically with publishing rights beyond those of a customer.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00302 23rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
creativethemeshqBlocksy Companionup to 2.1.58—No fix listedCNA
  • Blocksy Companion Vendorcreativethemeshq Affected up to 2.1.58 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Blocksy Companion.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-107645
  2. 2026-10-10 Alias added: GHSA-w5h9-m5j6-5394
  3. 2026-10-11 Priority changed: MEDIUM → LOW
  4. 2026-10-11 CISA SSVC decision points changed
  5. 2026-10-11 Priority changed: LOW → MEDIUM

References

  • TI-2026-42084 Blocksy Companion Pro < 2.1.47 Unauthenticated File Upload via save_attachments CVSS 4.0CRITICAL 9.2
  • TI-2023-01796 Blocksy Companion < 1.8.82 - Subscriber+ Draft Post Access CVSS 3.1MEDIUM 4.3
  • TI-2026-12769 Blocksy Companion <= 2.1.46 - Unauthenticated Arbitrary File Upload via 'blc-review-images[]' Parameter CVSS 3.1CRITICAL 9.8
  • TI-2026-41450 WordPress Blocksy Companion Pro plugin <= 2.1.46 - Remote Code Execution (RCE) vulnerability CVSS 3.1CRITICAL 10.0
  • TI-2026-28570 WordPress Blocksy Companion Pro plugin < 2.1.29 - SQL Injection vulnerability CVSS 3.1CRITICAL 9.3
  • TI-2026-29451 WordPress Blocksy Companion Pro plugin <= 2.1.37 - Remote Code Execution (RCE) vulnerability CVSS 3.1CRITICAL 9.9
See all 35 →

Sources