# Blocksy Companion <= 2.1.59 - Cross-Site Request Forgery to Extension Deactivation via Incorrect License Handler

- **ID:** WPSEC-2026-1114
- **Plugin:** Blocksy Companion (`blocksy-companion`), https://wordpress.org/plugins/blocksy-companion/
- **Affected versions:** all versions before 2.1.60
- **Fixed in:** 2.1.60 (Update to 2.1.60 or later.)
- **Severity:** Medium 4.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N)
- **Weakness:** CWE-352
- **Usage among sites WPSec scans:** plugin Medium, affected versions Medium (as of 2026-10-16)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/blocksy-companion
- **Fix released:** 2026-10-15
- **Published:** 2026-10-16
- **URL:** https://wpsec.com/vuln/WPSEC-2026-1114/

## Description

The Blocksy Companion plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.59 due to missing nonce validation on the blocksy_dashboard_handle_incorrect_license AJAX action, which deletes the active extensions option. This makes it possible for unauthenticated attackers to deactivate all of the plugin's extensions via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.

## References

- https://wpsec.com/vuln/WPSEC-2026-1114/
- https://plugins.svn.wordpress.org/blocksy-companion/tags/2.1.60/
- https://wordpress.org/plugins/blocksy-companion/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-1114/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.