Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege WordPress account
-
DeliverySubmit crafted input with stored script payload
-
ExploitPayload persisted by Blocksy Companion
-
ExecutionAdmin/victim views affected page
-
ImpactScript 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Blocksy Companion
View allRemote code execution in the Blocksy Companion Pro WordPress plugin (all versions before 2.1.47) lets unauthenticated at
Arbitrary file upload leading to remote code execution affects the premium Blocksy Companion Pro plugin for WordPress in
Unauthenticated privilege escalation in the Blocksy Companion WordPress plugin (versions up to and including 2.1.58) all
The Blocksy Companion WordPress plugin before 1.8.82 does not ensure that posts to be accessed via a shortcode are alrea
Unauthenticated attackers can exploit a broken access control flaw in the Blocksy Companion WordPress plugin versions up
Stored Cross-Site Scripting in the Blocksy Companion WordPress plugin (versions up to and including 2.1.51) allows authe
The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG uploads in versions up t
The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Newsletter widg
Cross-Site Request Forgery (CSRF) vulnerability in CreativeThemes Blocksy Companion.0.28. Rated medium severity (CVSS 5.
Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. No vendor pat
Server-Side Request Forgery (SSRF) vulnerability in Creative Themes Blocksy Companion blocksy-companion.0.42. Rated medi
Stored Cross-Site Scripting in the Blocksy Companion WordPress plugin (all versions through 2.1.45) enables authenticate
EUVD-2026-114002
GHSA-6vp9-3f45-8p8c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB