Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliveryAuthor form block with malicious SVG icon
-
ExploitSubmit pending post for review
-
ExecutionAdministrator previews the form
-
PersistStored SVG decoded and injected
-
ImpactJavaScript executes in admin 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 | Exploitation requires: (1) the Gutenverse Form plugin installed at a version before 3.0.11 with a form block using the SVG icon feature; (2) an authenticated account at Contributor level or higher under the attacker's control (self-registration must be open, or the account otherwise obtained); and (3) a higher-privileged user - typically an administrator reviewing a pending post - to view or preview the affected form, which triggers the unsanitized SVG decode-and-insert. Limiting factors: the attacker cannot act fully unauthenticated, the payload is inert until a victim with a more privileged session renders the form (required user interaction), and sites that disable open registration or restrict Contributor content review materially reduce exposure. |
| Impact | This is a moderate, authenticated stored XSS (CWE-79) in the Gutenverse Form WordPress plugin, best characterized as a real-but-conditional risk rather than an urgent emergency. The input CVSS vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H, 6.8) carries an internal inconsistency worth flagging: the description states exploitation requires only 'Contributor-level access and above,' which is a LOW-privilege WordPress role, yet the vector encodes PR:H - verify with vendor, as PR:L is more defensible and would raise the score. The vector also marks S:U (unchanged scope), but a stored payload that executes JavaScript in a separate victim's (administrator's) browser session is a classic scope-change case (S:C). EPSS is low at 0.19% (8th percentile), and the CVE is NOT on CISA KEV - there is no evidence of active exploitation. Countervailing that, publicly available exploit code exists (WPScan), lowering the skill barrier. The decisive mitigating factors are the authentication requirement (a Contributor account must exist) and required user interaction (a higher-privileged user must view or preview the malicious form). Net: prioritize patching on sites with untrusted Contributor-level accounts, but this is not a mass-exploitation, spray-and-pray threat. |
| Exploit ScenarioDerived | An attacker who holds (or phishes/registers for) a Contributor account authors a form block embedding an SVG icon crafted with malicious markup; because the plugin decodes and inserts the SVG into the page without sanitization, the JavaScript fires in the browser of any higher-privileged user who views or previews the pending content. When an administrator reviews the attacker's pending post, the script runs in their authenticated session, enabling actions such as creating a rogue admin or planting a backdoor. Public exploit code for this flaw is available via WPScan, reducing the effort required to reproduce it. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Stored cross-site scripting in the Gutenverse Form WordPress plugin before 3.0.11 lets authenticated users with Contributor-level access or higher plant malicious SVG icon markup in a form block, which the plugin decodes and inserts into the page without sanitization so the script executes in the browser session of any user who views or previews the form - typically an administrator reviewing a pending post. Exploitation is conditional: it requires the vulnerable plugin with an SVG-icon form block, an attacker-controlled Contributor account (open self-registration or an otherwise obtained account), and a higher-privileged victim who renders the form, so publicly available exploit code exists but the payload stays inert until a privileged session triggers it. The vendor patch is available in 3.0.11, EPSS is very low at 0.19% (8th percentile), and there is no indication of confirmed active exploitation (no CISA KEV listing), making this a moderate, real-but-conditional risk rather than an urgent emergency.
RemediationAI
Vendor-released patch: Gutenverse Form 3.0.11, so the primary action is to update the plugin to 3.0.11 or later (WordPress admin → Plugins, or WP-CLI wp plugin update gutenverse-form), then verify the installed version. If the update cannot be applied immediately, the most effective compensating control is to stop the SVG-icon feature from being used: remove SVG icon content from existing form blocks and instruct authors not to add it, since the stored markup is the payload carrier and leaving it in place keeps the site exploitable - the trade-off is loss of icon functionality in affected forms. Tighten the Contributor role in the interim (remove edit_posts/post-authoring capability via a role-editor plugin) or disable open self-registration, which removes the attacker's ability to provision the Contributor account the exploit requires, at the cost of disrupting contributor publishing workflows. Also avoid previewing or publishing pending posts and forms from untrusted contributors until patched, and audit existing posts, drafts and preview content for injected SVG/script markup and clean it out; blocking SVG markup at a WAF or content filter gives only partial coverage because the payload is stored server-side. Refer to the WPScan advisory at https://wpscan.com/vulnerability/4cccafbb-622e-4363-ade9-dc755d082a9f/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-106469 for update guidance.
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
Gutenverse Form is a WordPress form-builder plugin built on the block editor, and this is a stored cross-site scripting flaw (CWE-79: improper neutralization of input during web page generation) rooted in an unsafe render path rather than in the storage layer alone. SVG icon markup supplied through the plugin's form blocks is persisted with the post content, then decoded and inserted into the DOM client-side by JavaScript without sanitization - effectively an innerHTML-style sink for attacker-controlled markup - so any embedded script or event handler inside the SVG runs in the victim's authenticated session. Contributors (the WordPress role able to author draft/pending content) can seed the payload, and the code executes when a more privileged user previews or views the affected form, which is why the independent assessment rates it AV:N/AC:L/PR:L/UI:R/S:C with high confidentiality and integrity impact (the source CVSS instead used PR:H, understating that only Contributor privileges are needed). The CPE cpe:2.3:a:unknown:gutenverse_form confirms the affected artifact is the plugin package, with the vendor field unassigned in the dictionary; the CVE is catalogued by ENISA as EUVD-2026-100884.
Know when Gutenverse Form 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:H/UI:R/S:U/C:H/I:H/A:H
Contributor role is low-privilege so PR:L (not PR:H); an admin must view the form so UI:R; stored XSS executing in a separate session is a scope change (S:C); no direct availability impact so A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Gutenverse Form WordPress plugin before 3.0.11 does not sanitize SVG icon markup stored in its form blocks before it is decoded and inserted into the page in the browser, allowing authenticated users with Contributor-level access and above to store malicious SVG that executes JavaScript in the session of any user who views or previews the affected form, such as an administrator reviewing a pending post.
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.
EUVD-2026-100884
GHSA-77vr-jjv3-x5q5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB