CVE-2026-2951
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 Gutentor – Gutenberg Blocks – Page Builder for Gutenberg Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.5.5 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 Gutentor WordPress plugin versions up to 3.5.5 suffer from a stored XSS vulnerability due to insufficient input sanitization on user inputs and inadequate output escaping. Authenticated attackers with contributor-level permissions can inject malicious JavaScript into plugin settings or page content that executes whenever users access the 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Gutentor plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate Gutentor. Note the version number displayed. Alternatively, check the plugin files: /wp-content/plugins/gutentor/readme.txt or the plugin header in /wp-content/plugins/gutentor/gutentor.php contains the Version field.Affected if The installed version is 3.5.5 or lower (the CVE states versions up to and including 3.5.5 are affected)
-
Identify users with contributor-level permissionsIn WordPress admin, go to Users > All Users. Review the Role column for any accounts assigned the Contributor role. Also check for any custom roles that may have similar edit capabilities.Affected if There is at least one user with Contributor-level or higher permissions (since attackers need this access to inject the XSS)
-
Inspect Gutentor module and template settingsNavigate to Gutentor settings in the WordPress admin (typically under Gutentor > Settings or within individual page editor Gutentor blocks). Check all text fields, button labels, link URLs, and custom CSS/JS fields for any unexpected <script> tags, javascript: URLs, or onload/onerror event handlers.Affected if Any suspicious JavaScript code or event handlers are found in plugin settings that were not added by an administrator
-
Review pages and posts using Gutentor blocksEdit any page or post that uses Gutentor blocks. Inspect text elements, button links, image attributes, and custom code fields within the Gutentor blocks for injected malicious scripts. Check both the Visual and Text/Code editor views.Affected if Malicious script tags or event handlers are present in Gutentor block content on any published page
A user is affected if Gutentor plugin version 3.5.5 or lower is installed AND there is at least one Contributor-level or higher user account, allowing stored XSS to be injected into plugin settings or page content.
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.
From vendor dataUpdate the Gutentor plugin to the latest patched version immediately. Until a patch is available, restrict contributor-level user permissions and review plugin settings for any suspicious injected content.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2951 — 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-2951 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