CVE-2026-1395
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 Gutentools plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Post Slider block's block_id attribute in all versions up to, and including, 1.1.3. This is due to insufficient input sanitization and output escaping combined with a custom unescaping routine that reintroduces dangerous characters. 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 Gutentools WordPress plugin (versions up to 1.1.3) contains a stored XSS vulnerability in the Post Slider block's block_id attribute. The flaw stems from inadequate input sanitization combined with a custom unescaping routine that re-introduces dangerous characters, allowing authenticated Contributors to inject arbitrary JavaScript that executes when 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.
-
Check Gutentools plugin versionNavigate to WordPress admin > Plugins > Installed Plugins, locate Gutentools, and note the version number. Alternatively, check the plugin's main PHP file for the 'Version' header comment.Affected if The installed version is 1.1.3 or earlier (versions up to and including 1.1.3 are affected).
-
Identify Post Slider block usageSearch your WordPress content (posts, pages, custom post types) for blocks named 'gutentools/post-slider' or examine pages using the WordPress block editor for the Post Slider block.Affected if Any page, post, or template contains a Post Slider block from the Gutentools plugin.
-
Inspect block_id attribute valuesFor each Post Slider block found, enter edit mode and examine the block settings panel for the 'Block ID' or 'block_id' field. Also inspect the page's HTML source to locate data-block-id attributes or wrapper IDs containing the Post Slider block.Affected if The block_id contains unescaped special characters such as quotes (", '), angle brackets (<, >), or JavaScript event handlers (onclick, onerror, etc.).
-
Review Contributor-level user accountsGo to WordPress admin > Users and examine the list for any accounts with the Contributor role.Affected if There are users assigned the Contributor role who have permission to create or edit content containing the Post Slider block.
You are affected if the Gutentools plugin version is 1.1.3 or earlier AND any Post Slider block exists with a block_id containing unescaped special characters or if untrusted Contributor users have access to edit content with this block.
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 Gutentools plugin to version 1.1.4 or later, which should include proper input sanitization and removal of the dangerous custom unescaping routine. Until then, limit Contributor-level access and review pages using the Post Slider block.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1395 — 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-1395 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