Skip to main content

Blocksy Companion Pro EUVDEUVD-2026-41278

| CVE-2026-57624 CRITICAL
Code Injection (CWE-94)
2026-07-02 Patchstack GHSA-f3xf-x8w4-hfx8
10.0
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with Blocksy Companion Pro ≤2.1.46
  2. Delivery
    Send crafted HTTP request to vulnerable endpoint
  3. Exploit
    Inject arbitrary PHP code (CWE-94)
  4. Execution
    Server evaluates and executes payload
  5. Persist
    Deploy web shell / exfiltrate data
  6. Impact
    Pivot into hosting environment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation is possible against network-reachable installations of Blocksy Companion Pro at version 2.1.46 or earlier, per the CVSS vector (AV:N/AC:L/PR:N/UI:N) and the 'Unauthenticated RCE' description. The primary limiting factor is deployment scope: the target must be running the Pro (premium) plugin - not merely the free Blocksy Companion or the Blocksy theme - at an affected version, and the vulnerable endpoint must be reachable. The specific vulnerable feature, parameter, or configuration prerequisite is not detailed in the provided data and should be verified against the Patchstack advisory.

Impact

All available signals point to genuine high priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, score 10.0) indicates network-reachable, low-complexity exploitation with no privileges and no user interaction, plus a scope change reflecting impact beyond the vulnerable component. The CWE-94 code-injection class combined with the 'Unauthenticated RCE' description makes automated, reliable exploitation plausible. However, EPSS data was not provided, so exploitation probability could not be independently weighed, and the vulnerability is not listed in CISA KEV - there is no evidence of active exploitation. No public exploit code was referenced. In short: the theoretical risk is maximal and the barrier to exploitation is low, but real-world exploitation status is currently unconfirmed, so the priority rests on preventive patching rather than confirmed incident response.

Exploit ScenarioDerived

A remote attacker sends a single crafted HTTP request to a public WordPress site running Blocksy Companion Pro 2.1.46 or earlier, injecting code into a vulnerable plugin parameter that the server evaluates as PHP. With no authentication or user interaction required, the attacker gains arbitrary code execution and can deploy a web shell, exfiltrate the database, or pivot into the hosting environment. No public proof-of-concept has been identified at time of analysis, but the low-complexity, unauthenticated nature makes reliable exploitation straightforward once the sink is known.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 02, 2026

Unauthenticated remote code execution affects Creative Themes' Blocksy Companion Pro WordPress plugin in all versions up to and including 2.1.46, allowing remote attackers to inject and execute arbitrary code (CWE-94) without any authentication or user interaction. Rated CVSS 10.0 with a scope-changed vector, this is a maximum-severity flaw reported by Patchstack. No public exploit identified at time of analysis and it is not currently listed in CISA KEV, but the trivial exploitability of an unauthenticated RCE makes it a high-priority patching target.

RemediationAI

Upgrade Blocksy Companion Pro to a release newer than 2.1.46; the exact fixed version is not stated in the provided data, so administrators should consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/blocksy-companion-pro/vulnerability/wordpress-blocksy-companion-pro-plugin-2-1-46-remote-code-execution-rce-vulnerability) and the Creative Themes vendor portal to confirm and apply the latest patched build. Until patched, reduce exposure by restricting access to the WordPress site with a Web Application Firewall (Patchstack offers virtual patching for this CVE) and by limiting reachability of the plugin's endpoints; if the Pro plugin is not essential, deactivating and removing it eliminates the attack surface at the cost of losing its features. Because the injection is unauthenticated, IP allowlisting of administrative paths alone is insufficient - front-end request filtering or the plugin's removal are the meaningful controls.

Affected VersionsENISA

Blocksy Companion Pro n/a ≤2.1.46

Affected Packages

euvd blocksy_companion_pro no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Blocksy Companion Pro is the premium add-on plugin for the widely-used Blocksy WordPress theme ecosystem, extending it with features such as custom post types, advanced widgets, and site-building utilities. The affected component is identified by CPE cpe:2.3:a:creative_themes:blocksy_companion_pro. The root cause is classified as CWE-94 (Improper Control of Generation of Code, i.e. Code Injection), meaning attacker-controlled input reaches a code-evaluation or dynamic-execution sink within the plugin's PHP request handling, allowing an adversary to have server-side code interpreted and run. Because WordPress plugins execute in the context of the web application and underlying PHP runtime, successful code injection typically yields full application-level compromise.

Know when Blocksy Companion Pro gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 10.0 CRITICAL

Unauthenticated network code injection with no user interaction warrants AV:N/AC:L/PR:N/UI:N; RCE breaching the PHP/OS boundary beyond the plugin justifies S:C and full C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.46 versions.

Executive ViewAI

Why It Matters

Blocksy Companion Pro WordPress plugin (all versions ≤2.1.46) contains a critical unauthenticated remote code execution vulnerability (CVSS 10.0) that allows attackers to fully compromise affected web servers without credentials or user interaction. No public exploit identified at time of analysis, but the trivial exploitability of this unauthenticated RCE makes it an urgent remediation target. Any organization running this plugin faces immediate risk of data theft, site defacement, and lateral movement into internal networks.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Uninstall or disable the plugin immediately on all WordPress systems-no technical workaround fully eliminates unauthenticated RCE risk; (2) If plugin must remain active, restrict HTTP(S) access to plugin endpoints via Web Application Firewall rules and IP whitelist; (3) Implement network segmentation to contain lateral movement from compromised servers; (4) Enable enhanced logging and alerting for suspicious code execution patterns on web servers; (5) Maintain offline backups of all WordPress configurations and databases.

Threat Intelligence Overview

EPSS Score
0.7%
Top 51% exploitable
Prevalence
Medium
premium add-on for popular Blocksy WordPress theme; paid, narrower footprint
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy