Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit unauthenticated dynamic-content input
-
DeliveryPattern consumes attribute-closing quote
-
ExploitStored script injected into page markup
-
ExecutionPayload runs in admin/visitor browser
-
ImpactHijack administrator session
Vulnerability Assessment
| Weakness |
CWE
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 that affected pages use Otter Blocks' dynamic-content tokens, where the flawed rewrite pattern can reach the quote closing an HTML attribute with attacker-influenced unescaped data placed adjacently - that rendering path is the concrete prerequisite. Injection itself needs no authentication (PR:N), but the payload only fires when a visitor or logged-in administrator actually loads the affected page (UI:R), so a rendering victim is the key limiting factor. The exact conditions under which attacker data lands adjacent to the token are not fully detailed in the available sources; mitigation is upgrading to Otter Blocks 3.2.8 as the vendor provides. |
| Impact | Signals point to a moderate-priority issue rather than an emergency. The vuln.today Decision label is 'this_week', and the CISA SSVC framework records Exploitation: none and Automatable: no, with Technical Impact: total - i.e. no observed or reliable mass exploitation, but a serious impact if exploited. There is no CISA KEV listing and no EPSS score was supplied, so widespread exploitation is not indicated. No PoC or exploit reference is present (the only links are the WPScan advisory and the NVD page), so exploitation status is 'no public exploit identified at time of analysis'. The supplied CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, score 7.5) is internally questionable for a stored XSS: it claims full C:H/I:H/A:H with S:U (unchanged scope), whereas an XSS that executes in a victim's browser normally carries limited confidentiality/integrity impact and a changed scope - the C:H/I:H/A:H rating appears inflated and should be verified with the vendor/WPScan. The PR:N value does confirm the injection step is unauthenticated, and UI:R confirms a victim must render the affected page. Net: a credible, fixable stored-XSS with realistic admin-takeover consequences, warranting prompt patching on the stated this_week timeline, but not currently evidenced as actively or automatically exploited. |
| Exploit ScenarioDerived | An unauthenticated attacker submits data that Otter Blocks later renders through its dynamic-content token rewriting; the unbounded pattern consumes the quote closing an HTML attribute and pulls the adjacent unescaped data into the markup as a new attribute carrying a script payload. When any visitor - notably a logged-in administrator - views the affected page, the payload executes in their browser (UI:R), enabling session or action hijacking. No public exploit code is confirmed; only the WPScan advisory exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
Stored cross-site scripting in the Otter Blocks WordPress plugin before 3.2.8 allows unauthenticated attackers to plant markup that executes in the browser of any visitor - including a logged-in administrator - who views an affected page. The flaw sits in the block-rendering rewrite of dynamic-content tokens, where an improperly bounded pattern can consume the quote that closes an HTML attribute and pull adjacent unescaped data into the markup as new attributes. Exploitation requires that affected pages actually use the dynamic-content tokens and that a victim loads the page; no public exploit has been identified at time of analysis, and the CISA SSVC assessment records exploitation as none.
RemediationAI
Vendor-released patch: upgrade the Otter Blocks plugin to version 3.2.8 or later, which corrects the dynamic-content token rewrite pattern. The vendor advisory at https://wpscan.com/vulnerability/c9f264ad-0857-4d1f-9f20-694469d7bee0/ documents the fix, and no separate workaround is described in the available sources, so updating is the complete remediation. Because the payload is stored and fires for any visitor of an affected page, prioritize sites that use Otter Blocks' dynamic-content tokens and audit existing block content for injected attributes after upgrading.
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
Otter Blocks is a Gutenberg block library for WordPress that renders dynamic content by substituting tokens inside block markup at render time. The rewrite uses a pattern that is not correctly bounded, so it can run past the intended token boundary, consume the quote terminating an HTML attribute, and treat adjacent attacker-influenced, unescaped data as new attributes - a CWE-79 improper neutralization of input during web page generation issue. Because the injection is stored and re-rendered on every page view, the script executes in the context of the site's origin for any visitor, including administrators. The CVSS vector confirms remote, unauthenticated injection (AV:N/PR:N) with user interaction (UI:R), and the independent assessment applies a scope change (S:C) with low confidentiality and integrity impact, reflecting script execution in the victim's browser rather than server compromise. The precise conditions under which attacker-controlled data lands adjacent to the token during the rewrite are not fully detailed in the available sources; the vendor-supplied fix in 3.2.8 addresses the pattern bounding.
Know when WordPress 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:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated injection (PR:N) but the script runs only when a victim renders the page (UI:R) in their browser's separate security context (S:C), giving limited C/I and no availability impact - typical stored-XSS profile.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
3DescriptionCVE.org
The Otter Blocks WordPress plugin before 3.2.8 does not correctly bound a pattern it uses to rewrite its dynamic-content tokens while rendering blocks, so the pattern can consume the quote that closes an HTML attribute and pull adjacent unescaped data into the markup as new attributes. This allows unauthenticated users to achieve stored Cross-Site Scripting that executes in the browser of any visitor who views an affected page, including a logged-in administrator.
Executive ViewAI
A stored cross-site scripting vulnerability in the Otter Blocks WordPress plugin (versions before 3.2.8) enables unauthenticated attackers to inject persistent code that executes when any user, including administrators, views an affected page. Successful exploitation could lead to session hijacking or full site compromise, undermining trust in the organization's web presence and potentially exposing sensitive data.
Apply vendor patch.
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.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The 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 GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
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
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-108589
GHSA-7hjg-79p8-hrjm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB