Skip to main content

Blocksy Companion EUVDEUVD-2026-114002

| CVE-2026-65444 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-30 Patchstack GHSA-6vp9-3f45-8p8c
6.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privilege WordPress account
  2. Delivery
    Submit crafted input with stored script payload
  3. Exploit
    Payload persisted by Blocksy Companion
  4. Execution
    Admin/victim views affected page
  5. Impact
    Script executes in victim browser context

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

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

Exploitation Conditions

Exploitation requires an authenticated WordPress account with low privileges (PR:L - e.g. contributor or author able to submit content the plugin stores), and it requires victim user interaction (UI:R): a second user must load the page where the payload is stored for the script to execute. The specific plugin feature or input field that fails to neutralize the input is not described in the available sources. Limiting factors that reduce real-world risk: the attacker cannot be fully unauthenticated, the payload only triggers when another user views the content, and impact is confined to the browser context of that viewer (Low C/I/A) rather than direct server compromise. It affects Blocksy Companion from an unspecified earlier version through 2.1.60.

Impact

This is a moderate-severity stored cross-site scripting (XSS) issue (CWE-79) in the Blocksy Companion WordPress plugin, scored CVSS 6.5. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L tells a nuanced story: the attack is network-reachable with low complexity, but it is NOT unauthenticated - PR:L means the attacker must already hold a low-privilege authenticated account (typically a contributor/author-level WordPress user), and UI:R means a victim must view the page where the payload is stored before it fires. The scope change (S:C) and Low ratings across confidentiality, integrity and availability reflect that the injected script executes in another user's browser context (e.g. an administrator) rather than directly compromising the server. On real-world signals: there is no CISA KEV listing and no EPSS probability supplied, so there is no evidence of active or widespread exploitation; the vuln.today decision label is 'this_month', i.e. a routine prioritized patch rather than an emergency. The only reference is a Patchstack advisory, not confirmed working exploit code. Net assessment: a legitimate issue to patch on a normal cadence, but the authentication prerequisite and required user interaction meaningfully lower real-world urgency compared to the headline 'network XSS' framing. No EPSS or KEV data was provided to contradict or reinforce this, which is itself a gap.

Exploit ScenarioDerived

An attacker who holds a low-privilege authenticated account (such as a contributor) on a WordPress site running Blocksy Companion ≤ 2.1.60 submits content containing a malicious script payload that is stored by the plugin without proper neutralization. When a higher-privileged user such as an administrator later views the affected page in the dashboard or front end, the script executes in their browser, potentially enabling session/action abuse within the admin's context. No public working exploit code is identified in the provided data, only a Patchstack advisory.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 30, 2026

Stored cross-site scripting in the Blocksy Companion WordPress plugin (versions through 2.1.60) allows an authenticated low-privilege user to persist script that runs when another user views the affected page. The CVSS 3.1 score is 6.5 with PR:L and UI:R, so the attacker needs a WordPress account able to store content and the victim must load it; no public exploit was identified at time of analysis.

RemediationAI

The available data does not state the first fixed version; it only identifies Blocksy Companion versions through 2.1.60 as affected. Apply the vendor update for Blocksy Companion and confirm the patched release in the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/blocksy-companion/vulnerability/wordpress-blocksy-companion-plugin-2-1-60-cross-site-scripting-xss-vulnerability?_s_id=cve) before deployment. No feature-specific workaround is documented in the supplied sources because the vulnerable plugin input is not described; as a stopgap, limit low-privilege WordPress roles such as contributor or author accounts that can store content rendered by the plugin, accepting that this can disrupt editorial workflows and may not cover every stored-content path. No vendor-released fixed version is specified in the available data.

Affected VersionsENISA

Blocksy Companion 0 ≤2.1.60

Affected Packages

euvd blocksy_companion 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 is a Creative Themes WordPress plugin; CVE-2026-65444 is CWE-79 improper neutralization of input during web page generation, specifically stored XSS. The CPE cpe:2.3:a:creative_themes:blocksy_companion:*:*:*:*:*:*:*:* identifies the plugin, and the advisory covers versions from n/a through 2.1.60. The specific vulnerable input path is not described in the available sources: what is confirmed is that an authenticated low-privilege account (PR:L) can store content the plugin renders, and a second user must load that page (UI:R), after which script executes in the victim's browser with scope changed (S:C) and low confidentiality, integrity, and availability impact. This is a client-side browser-context issue, not direct server compromise, and no public exploit was identified at time of analysis.

Know when Blocksy Companion 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 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.5 MEDIUM

Stored XSS reachable over the network by a low-privilege authenticated user (PR:L), requiring a victim to view the content (UI:R), executing in the victim's browser (S:C) with limited C/I/A impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
popular WordPress companion plugin for the widely-used Blocksy theme
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2026-58480 CRITICAL POC
9.2 Jul 08

Remote code execution in the Blocksy Companion Pro WordPress plugin (all versions before 2.1.47) lets unauthenticated at

CVE-2026-15158 CRITICAL
9.8 Jul 09

Arbitrary file upload leading to remote code execution affects the premium Blocksy Companion Pro plugin for WordPress in

CVE-2026-107645 CRITICAL
9.1 Oct 10

Unauthenticated privilege escalation in the Blocksy Companion WordPress plugin (versions up to and including 2.1.58) all

CVE-2023-1911 MEDIUM POC
4.3 May 02

The Blocksy Companion WordPress plugin before 1.8.82 does not ensure that posts to be accessed via a shortcode are alrea

CVE-2026-97247 MEDIUM
6.5 Sep 30

Unauthenticated attackers can exploit a broken access control flaw in the Blocksy Companion WordPress plugin versions up

CVE-2026-18488 MEDIUM
6.4 Sep 01

Stored Cross-Site Scripting in the Blocksy Companion WordPress plugin (versions up to and including 2.1.51) allows authe

CVE-2024-4487 MEDIUM
6.4 May 14

The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG uploads in versions up t

CVE-2024-2392 MEDIUM
6.4 Mar 22

The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Newsletter widg

CVE-2024-31932 MEDIUM
5.4 Apr 11

Cross-Site Request Forgery (CSRF) vulnerability in CreativeThemes Blocksy Companion.0.28. Rated medium severity (CVSS 5.

CVE-2023-23898 MEDIUM
5.4 Apr 06

Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor pat

CVE-2024-35633 MEDIUM
4.4 Jun 03

Server-Side Request Forgery (SSRF) vulnerability in Creative Themes Blocksy Companion blocksy-companion.0.42. Rated medi

CVE-2026-12430 MEDIUM
4.4 Jun 19

Stored Cross-Site Scripting in the Blocksy Companion WordPress plugin (all versions through 2.1.45) enables authenticate

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