Blocksy Companion Pro <= 2.1.37 - Authenticated (Contributor+) Remote Code Execution
Strategic Overview
- Status
- Patched in 2.1.38
- Affected Plugin
- Blocksy Companion Pro
- Affected Version
<= 2.1.37- CVSS
- 4.3Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2026-40783
At a glance
CVE-2026-40783 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Blocksy Companion Pro WordPress plugin, affecting versions <= 2.1.37. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.1.38; sites on affected versions should update now. Disclosed April 2026, reported by Nguyen Ba Khanh.
Vulnerability Overview
The Blocksy Companion Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.1.37. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Blocksy Companion Pro <= 2.1.37 takes an account at Contributor level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Blocksy Companion Pro the fix is 2.1.38: builds <= 2.1.37 are affected, anything from 2.1.38 onward is not.
Remediation
Update to version 2.1.38, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Blocksy Companion Pro 2.1.38 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Blocksy Companion Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C