Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as contributor-level user
-
ExploitInject payload via 'data-image-points' parameter
-
ExecutionStore unsanitized script in page content
-
ImpactExecute in victim browser on page view
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 account with contributor-level privileges or higher on a WordPress site running the Getwid - Gutenberg Blocks plugin version 3.0.1 or earlier, and the attacker must be able to author/edit block content that uses the affected 'data-image-points' parameter. The stored payload only fires when another user (e.g., an administrator, editor, or visitor) subsequently accesses the injected page, so impact depends on a victim viewing the content. Key limiting factors: the required contributor-level authentication (per PR:L) restricts this to sites that provision low-trust author accounts; sites with only a single administrator and no open registration or contributor roles face little practical exposure. |
| Impact | This is a moderate-severity Stored XSS (CVSS 6.4, CWE-79) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. The AV:N/AC:L/UI:N combination suggests easy remote exploitation, but PR:L is the decisive limiter: the attacker must already hold a contributor-level (or higher) authenticated account on the target WordPress site, which materially narrows the realistic attacker population to sites that provision such accounts. The scope change (S:C) and low confidentiality/integrity impact reflect typical stored-XSS behavior - payload executes in the browser of whoever views the injected page, crossing the security boundary from the authoring context to the victim's session. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no public exploit identified at time of analysis. No SSVC decision data was supplied. Net assessment: a genuine but not emergency-priority issue - it ranks below unauthenticated or admin-impact flaws. Priority rises on multi-author sites (membership, multi-contributor blogs, agencies) where low-trust accounts exist; it is near-negligible on single-admin sites where no contributor accounts are issued. Signals are internally consistent - no conflict between CVSS and description. |
| Exploit ScenarioDerived | An attacker who has obtained or been granted a contributor-level account on a WordPress site running Getwid ≤3.0.1 crafts a block containing a malicious payload in the 'data-image-points' parameter, which is stored without adequate sanitization. When an administrator, editor, or site visitor later views the page, the script executes in their browser context, enabling session hijacking, credential theft, or privilege escalation toward site takeover. No public exploit code is identified at time of analysis, and exploitation requires an existing low-privilege authenticated account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Stored cross-site scripting in the Getwid - Gutenberg Blocks plugin for WordPress (all versions up to and including 3.0.1) allows authenticated attackers with contributor-level privileges or higher to inject arbitrary web scripts through the 'data-image-points' parameter, which are then stored and executed whenever another user - an editor, administrator, or site visitor - accesses the affected page. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N confirms the attacker needs a low-privileged authenticated account but requires no victim interaction to trigger the payload beyond viewing the injected page, and the changed scope indicates the script executes in the context of the broader site rather than the attacker's own content. No public exploit code has been identified at the time of analysis and there is no indication of confirmed active exploitation (CISA KEV), so practical exposure is concentrated on sites that provision contributor accounts to untrusted users or allow open registration; a site with only a single administrator and no contributor roles faces minimal real-world risk.
RemediationAI
Update the Getwid - Gutenberg Blocks plugin to a build containing plugin repository changeset 3698562 or later - the upstream fix is available as that changeset (Upstream fix available (PR/commit); released patched version not independently confirmed), so verify the installed plugin version in wp-admin or via WP-CLI after updating and confirm the changeset is included before assuming the site is clean. If the plugin cannot be updated immediately, the most effective compensating control is to remove or deactivate Getwid, which eliminates the injection surface at the cost of losing all Getwid blocks on existing content; a less disruptive option is to audit and restrict contributor-level accounts - disable open registration, downgrade or remove untrusted contributor users, and require editorial review before contributor content is published - accepting that this does not fix the underlying sanitization flaw. Additional hardening with its own trade-offs includes scanning existing posts and post meta for suspicious 'data-image-points' values and cleaning any injected payloads (needed because stored XSS persists after patching), and deploying a WAF rule that blocks script-bearing attribute patterns in post submissions (useful but prone to false positives on legitimate block content). Because the payload executes for the viewing user, also advise administrators to review the site for unexpected content and rotate any credentials or sessions that may have been exposed. Consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/95c421a8-b945-424b-bd8e-e95691be2c04?source=cve) and the fixed changeset (https://plugins.trac.wordpress.org/changeset/3698562) for the authoritative vendor details; no vendor-released patch version string was independently confirmed from the provided data, so do not rely on an invented version number.
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
This is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) defect affecting a WordPress Gutenberg block plugin. Getwid registers custom blocks whose attributes - in this case an image-points style parameter surfaced as 'data-image-points' - are persisted with the post content (as block attributes and/or post meta) and later rendered into the front-end and editor markup. Because the plugin neither sanitizes the attribute on input nor escapes it on output, a contributor-level user can store a string that breaks out of the attribute context and injects executable script. The CVSS scope change (S:C) reflects that the injected script runs in the origin of the victim WordPress site, giving it access to that site's DOM, cookies, and any privileged AJAX actions available to the viewing user - a standard escalation path for stored XSS in CMS plugins. The affected product is identified by CPE cpe:2.3:a:jetmonsters:getwid_-_gutenberg_blocks (vendor jetmonsters, version wildcarded), reported by Wordfence. The vector's PR:L and UI:N mean exploitation requires an authenticated low-privilege account but no additional user action to deliver the payload - persistence in the page is the delivery mechanism, and the payload fires on the victim's subsequent page load.
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 authentication is required so PR:L; stored payload executes without the attacker's further interaction (UI:N), crosses into victim's browser context (S:C), yielding limited C/I impact and no availability loss.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data-image-points' parameter in all versions up to, and including, 3.0.1 due to insufficient input sanitization and output escaping. 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 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
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96101
GHSA-qrfh-5pfh-hxq5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB