Cpe:2.3:a:creativethemes:blocksy_companion:*:*:*:*:*:wordpress:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3acreativethemesblocksy_companionwordpress/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 10 Oct 2026 05:33:51 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnauthenticated Privilege Escalation in Blocksy Companion Plugin for WordPresshttps://feed.craftedsignal.io/briefs/2026-10-blocksy-privilege-escalation/Sat, 10 Oct 2026 05:33:51 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-blocksy-privilege-escalation/The Blocksy Companion WordPress plugin is vulnerable to unauthenticated privilege escalation, allowing attackers to create arbitrary vendor accounts by bypassing Dokan registration security checks.The Blocksy Companion plugin for WordPress, in versions up to and including 2.1.58, contains a critical vulnerability (CVE-2026-107645) that enables unauthenticated privilege escalation. The vulnerability resides in the implement_user_registration() AJAX handler, which incorrectly disables the Dokan vendor-registration nonce check by executing add_filter('dokan_register_nonce_check', '__return_false').

By sending a specially crafted request to this endpoint, an unauthenticated attacker can supply an arbitrary role parameter to wc_create_new_customer() and wc_set_customer_auth_cookie(). This process ignores site-wide settings that may have disabled vendor registration, automatically creating and authenticating a user with 'seller' (vendor) privileges. This grants the attacker elevated publishing capabilities on the affected WordPress site, significantly expanding their control beyond that of a standard customer. Because this exploit operates via the public-facing AJAX handler, it is accessible to any remote, unauthenticated user, representing a high risk for sites running the vulnerable plugin configuration.

Attack Chain

  1. Attacker identifies a target WordPress site running the vulnerable Blocksy Companion plugin (version <= 2.1.58) with the Dokan plugin enabled.
  2. Attacker crafts an HTTP POST request targeting the AJAX action associated with implement_user_registration().
  3. The request includes a malicious role parameter set to the 'seller' or 'vendor' role identifier.
  4. The plugin's vulnerable AJAX handler executes, explicitly disabling the Dokan nonce validation filter.
  5. The plugin invokes wc_create_new_customer() with the attacker-controlled role parameter.
  6. The WordPress backend registers the new account and the wc_set_customer_auth_cookie() function is invoked.
  7. The attacker receives an authentication cookie, allowing them to access the site with vendor-level publishing permissions.

Impact

Successful exploitation allows unauthenticated users to gain unauthorized access to 'seller' or 'vendor' accounts on WordPress sites integrated with the Dokan plugin. This provides attackers with publishing capabilities, potentially leading to unauthorized content injection, cross-site scripting (XSS) vectors, or further exploitation of administrative functionality accessible to the vendor role. Any site utilizing Blocksy Companion and Dokan simultaneously is exposed to this risk.

Recommendation

  • Upgrade the Blocksy Companion plugin to the latest available version beyond 2.1.58 immediately.
  • Monitor server access logs for anomalous POST requests to WordPress AJAX endpoints originating from unauthenticated sessions.
  • Verify that Dokan vendor registration settings are explicitly managed by administrative policy rather than plugin-level overrides.
]]>criticaladvisorywordpressprivilege-escalationweb-application