Blocksy Companion vulnerabilities

Unauthenticated Broken Access Control vulnerability in Blocksy Companion versions up to 2.1.55.

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.

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.

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Creative Themes Blocksy Companion blocksy-companion allows Stored XSS. This issue affects Blocksy Companion: from n/a through 2.1.60.

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.

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.