CVE-2026-2868
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Gutenverse – Ultimate WordPress FSE Blocks Addons & Ecosystem plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'separatorIconSVG' parameter in versions up to, and including, 3.5.3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Gutenverse WordPress plugin fails to properly sanitize the 'separatorIconSVG' parameter during input and escape it during output, allowing stored XSS. An authenticated attacker with contributor-level access can inject malicious JavaScript via SVG content that executes when other users view affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Gutenverse plugin is installedNavigate to WordPress Admin > Plugins or use WP-CLI: wp plugin list --name=gutenverseAffected if Plugin is active and installed without a version past 3.5.3
-
Confirm installed version numberCheck the plugin version displayed in the plugin list or run: wp plugin get gutenverse --field=versionAffected if Version is 3.5.3 or lower, indicating unpatched installation
-
Identify contributor-level usersNavigate to WordPress Admin > Users and filter by Contributor role, or run: wp user list --role=contributorAffected if At least one contributor-level user account exists in the system
-
Inspect posts for Gutenverse block dataQuery the wp_postmeta table for meta keys containing 'gutenverse' and inspect the meta_value for separatorIconSVG fields, or use: wp post meta list --meta_key=_gutenverse_settingsAffected if Any post contains separatorIconSVG parameter data with unsanitized SVG content (check for <script> tags or javascript: handlers)
-
Verify XSS payload presence in databaseSearch post meta for patterns like 'onerror=', 'onload=', 'javascript:', or '<script' within SVG-related meta valuesAffected if Malicious JavaScript code is found stored in meta fields containing SVG configuration
You are affected if Gutenverse plugin version 3.5.3 or lower is installed AND contributor-level users exist AND separatorIconSVG data with unsanitized SVG or script tags is present in post meta.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to a version past 3.5.3 which includes proper sanitization for SVG input (e.g., sanitize_text_field or dedicated SVG sanitization) and ensure all output uses proper escaping functions.
Latest version available (greater than 3.5.3) from WordPress plugin repository
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Gutenverse plugin
- Check if an update is available and update to the latest version
- Alternatively, download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data