Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor account on target site
-
DeliveryInject script into vulnerable block attribute
-
ExploitSubmit post for review/preview
-
ExecutionAdmin or editor opens content in wp-admin
-
PersistPayload executes in privileged session
-
ImpactSteal session tokens or perform admin actions
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 | Requires an authenticated WordPress account with at least Contributor privileges on a site running Premium Blocks - Gutenberg Blocks for WordPress version 2.3.17 or earlier. Exploitation is gated by user interaction (UI:R): a higher-privileged user such as an editor or administrator must view or preview the attacker's injected block content in wp-admin for the stored script to execute. Practical limiting factors are the need for a foothold account (sites with closed registration or no untrusted authors are largely insulated) and the victim-interaction requirement; there is no unauthenticated path. |
| Impact | This is a moderate-severity stored/contributor Cross-Site Scripting flaw (CWE-79) in a WordPress block plugin, scored 6.5 by the vendor with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L. The key risk-limiting signals are PR:L (an authenticated Contributor-level account is required) and UI:R (a victim - typically an editor or administrator - must view the injected content for the payload to fire). No EPSS score is provided, there is no CISA KEV listing, and no public proof-of-concept is referenced (the only reference is the Patchstack advisory), so this is 'no public exploit identified at time of analysis.' The S:C (scope change) reflects that script executing in a higher-privileged user's authenticated browser session crosses a trust boundary, but real-world impact is bounded to C:L/I:L/A:L. Overall this is a real but low-urgency issue: it is not a high-CVSS-but-fictional problem, yet it is far from a mass-exploitation candidate because it needs a foothold account plus victim interaction. The A:L component is questionable for a reflected/stored XSS and is likely vendor over-scoring; realistic impact is confidentiality/integrity of the admin session, not availability. Prioritize patching on multi-author sites where untrusted Contributor accounts exist; deprioritize on single-author/closed-registration sites. |
| Exploit ScenarioDerived | An attacker who holds (or registers for) a Contributor account on a WordPress site running Premium Blocks ≤ 2.3.17 crafts a post or block containing a malicious script payload in an inadequately sanitized block attribute. When an editor or administrator previews or opens that content in wp-admin, the script executes in their authenticated browser session, enabling session/cookie theft or admin-context actions. No public PoC is referenced, and exploitation requires the low-privilege account plus victim interaction (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Stored cross-site scripting in the Premium Blocks - Gutenberg Blocks for WordPress plugin (versions up to and including 2.3.17) lets an authenticated Contributor-level user inject persistent JavaScript into block content that executes when a higher-privileged editor or administrator later views or previews that content in wp-admin. Exploitation requires a foothold account with Contributor privileges and victim interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, 6.5), with low confidentiality and integrity impact and no availability impact; sites that do not accept untrusted author accounts are largely insulated. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor-released patch version is specified in the available intelligence.
RemediationAI
No vendor-released patch version is identified in the available intelligence at time of analysis, so administrators should check the Patchstack advisory and the plugin's WordPress.org page regularly and apply the fixed release immediately once it is published (upgrade beyond 2.3.17 to the patched version). In the interim, reduce the attack surface by disabling or removing the Premium Blocks - Gutenberg Blocks for WordPress plugin if it is not business-critical; if it must remain, restrict or eliminate Contributor-level accounts on the site, disable open user registration and any untrusted author onboarding, and audit existing Contributor-authored drafts for injected script content before editors or administrators preview them. Additional compensating controls include removing the Contributor role's capability to use the affected blocks, deploying a web application firewall rule set that filters XSS patterns in block or post-save requests (trade-off: may cause false positives on legitimate rich content), and advising privileged users not to preview or open untrusted contributor drafts until the plugin is updated. Each of these mitigations is temporary and does not fully eliminate the flaw, so the definitive remediation is installing the vendor's fixed plugin version once it is available; reference the Patchstack advisory for update status and further details.
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
The affected component is a WordPress Gutenberg block plugin, Premium Blocks - Gutenberg Blocks for WordPress (vendor leap13), identified by the CPE string cpe:2.3:a:leap13:premium_blocks_-_gutenberg_blocks_for_wordpress:*:*:*:*:*:*:*:*. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., Cross-Site Scripting): user-supplied block attributes or content are stored and later rendered without sufficient output escaping or sanitization in the administrative context. Because WordPress grants Contributor accounts the ability to create and save post content, but not publish it, a Contributor can inject the payload into a draft or pending post's block data; when an editor or administrator opens the preview or editor view, the script executes in their browser session. The scope-change rating (S:C) reflects that the injected script executes in the higher-privileged user's authenticated wp-admin context, enabling actions with that user's privileges, though the assessed confidentiality and integrity impact remains low and availability is unaffected. The vulnerability is submitted to WordPress by authenticated users (PR:L) and is gated by victim interaction (UI:R), so it is a stored, cross-privilege XSS rather than an unauthenticated remote code execution issue.
Know when Wordpress Plugin 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
Contributor account gives PR:L, admin must view content so UI:R, script in privileged session crosses trust boundary S:C with C:L/I:L; XSS does not cause availability loss so A:N.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Cross Site Scripting (XSS) in Premium Blocks - Gutenberg Blocks for WordPress <= 2.3.17 versions.
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 Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-85471
GHSA-3mrj-f84p-fphg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB