Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account on target WordPress site
-
DeliveryAdd News Ticker block with crafted clientId payload
-
ExploitclientId concatenated into class attribute without esc_attr()
-
ExecutionStore injected page/post
-
PersistAdmin or visitor opens page
-
ImpactScript executes in victim browser session
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 account with contributor-level capability or higher on a WordPress site running Magazine Blocks (by wpblockart) version 1.8.6 or earlier, with the block editor available to that account. The attacker must be able to add/edit content containing a News Ticker block, whose clientId attribute reaches NewsTicker::render() unescaped. Exploitation is limited by this authentication requirement (PR:L), so single-author or tightly-controlled sites are not exposed to arbitrary attackers; sites permitting open contributor registration, guest posting, or lower-trust editorial roles are the realistic risk surface. No user interaction is needed to store the payload, and it fires automatically when any viewer loads the injected page. |
| Impact | This is a genuine but moderate-priority issue, not an inflated high-CVSS finding. The vendor CVSS 3.1 vector (6.4, AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) is well-calibrated and I concur with it: network attack vector and low complexity are offset by PR:L (contributor-level authentication is required - this is NOT unauthenticated). The scope change (S:C) plus C:L/I:L correctly reflect stored XSS where injected script crosses from the plugin's rendering context into any viewer's browser session. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data - exploitation status is therefore 'no public exploit identified at time of analysis.' However, the Wordfence advisory and the trac source lines (NewsTicker.php#L43/#L106) plus the fix changeset (3656574) effectively document the vulnerable code path, lowering the bar for exploit development. The realistic risk is bounded by the contributor-access precondition, which limits this to multi-author sites, membership sites, or environments where lower-trust accounts can be registered. No signals conflict: the CVSS network vector is consistent with a web-delivered stored-XSS payload. |
| Exploit ScenarioDerived | An attacker holding (or self-registering) a contributor-level account on a WordPress site running Magazine Blocks <=1.8.6 inserts a News Ticker block and supplies a malicious clientId value containing a break-out sequence and script payload. Because NewsTicker::render() concatenates clientId into an HTML class attribute without esc_attr(), the payload is stored and later executed in the browser of any user - including an editor or administrator - who views the injected page. No public POC is identified, but the referenced source lines and fix changeset disclose the exact vulnerable sink. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Stored cross-site scripting in the Magazine Blocks WordPress plugin (wpblockart) through version 1.8.6 lets an authenticated user with contributor-level access or higher store arbitrary JavaScript that executes in the browser of anyone viewing the affected page. The flaw sits in the News Ticker block, where the block's clientId attribute is concatenated into an HTML class attribute inside NewsTicker::render() without esc_attr(), so the payload is persisted in post content rather than reflected. Exploitation requires a valid low-privilege account plus access to the block editor, which limits exposure to multi-author sites with open contributor registration or low-trust editorial roles; no public exploit code, EPSS signal, or CISA KEV entry was identified at time of analysis, and this is a genuine but moderate-priority issue rather than an inflated high-severity finding.
RemediationAI
Apply the upstream fix for the News Ticker render path - a WordPress.org plugin repository changeset addressing this issue is referenced (https://plugins.trac.wordpress.org/changeset?reponame=&old=3656574%40magazine-blocks&new=3656574%40magazine-blocks), but the specific patched release number is not identified in the available data, so update Magazine Blocks to the latest available version above 1.8.6 and confirm the deployed version thereafter. Wordfence's advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/34e0862d-55d3-4bc7-ba26-309ef1567e2b?source=cve should be checked for the exact fixed version as it is published, since the plugin may be vulnerable beyond the reported 1.8.6 boundary only until the fix is installed. Where immediate patching is not possible, compensating controls should target the contributor-level prerequisite: disable open contributor self-registration and audit existing contributor and author accounts (trade-off: reduces editorial throughput on multi-author sites), and treat all contributor-submitted content as untrusted until an editor reviews and publishes it, since unapproved drafts and previews are the most likely vector for the stored payload to reach a privileged viewer. If the ticker is not in active use, deactivating the plugin or removing the News Ticker block from layouts eliminates the vulnerable render path entirely (trade-off: loss of all other Magazine Blocks functionality, which is significant if the plugin powers site layout). A WAF rule or content filter that rejects or encodes raw event-handler and script markup inside class attribute values in block content offers partial protection but is easily bypassed by encoding tricks, so it should be paired with the patch rather than relied upon alone.
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
Magazine Blocks is a WordPress Gutenberg block library distributed through the WordPress.org plugin repository (CPE cpe:2.3:a:wpblockart:magazine_blocks_-_blog_designer,_magazine_&_newspaper_website_builder,_page_builder_with_posts_blocks,_post_grid). Its News Ticker block receives a clientId value that WordPress's block editor generates client-side and stores as a block attribute in serialized post content. The vulnerable code path, NewsTicker::render(), interpolates that attribute directly into the HTML class attribute of the rendered ticker element. Because the value is neither sanitized on input nor escaped with esc_attr() on output, an attacker who can author block content can close the class attribute and inject markup or script. This is a textbook CWE-79 cross-site scripting instance - improper neutralization of user-controlled data during web page generation - and the stored nature of the payload means the script persists in the database and re-executes on every page view. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects low complexity, a low-privilege authenticated requirement, no user interaction, and a scope change because injected script runs in the victim's browser context against the site.
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:N/S:C/C:L/I:L/A:N
Contributor account required (PR:L), no interaction to plant the stored payload (UI:N), and stored XSS crossing into the viewer's browser context yields S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Magazine Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the News Ticker block's clientId attribute in versions up to, and including, 1.8.6. This is due to insufficient input sanitization and output escaping in the NewsTicker::render() method, which concatenates the clientId block attribute into an HTML class attribute without applying esc_attr(). This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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-82744
GHSA-3rwr-qrj8-m997
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB