CVE-2026-11402
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 Services Section Block – Showcase Service Details in Grid or Columns plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'link' Block Attribute in all versions up to, and including, 1.4.4 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. The payload persists inside HTML comments in post_content, bypassing wp_kses_post sanitization at save time, and executes via both the primary service link anchor and a secondary title-wrapped anchor when the linkIn option is set to 'title'.
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 Services Section Block WordPress plugin versions up to 1.4.4 suffer from a stored XSS vulnerability in the 'link' Block Attribute. Authenticated attackers with contributor-level permissions can inject malicious JavaScript payloads that persist inside HTML comments in post_content, bypassing wp_kses_post sanitization at save time. The injected scripts execute via the primary service link anchor and also via a secondary title-wrapped anchor when the linkIn option is set to 'title'.
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.
-
Locate the plugin and determine its versionNavigate to wp-content/plugins/services-section-block/ and open the main PHP file. Look for the 'Version:' header in the plugin file comments to find the installed version number.Affected if The installed version is 1.4.4 or any version below it, since the vulnerability affects versions up to 1.4.4.
-
Identify posts using the services section blockQuery the WordPress wp_posts table for entries where post_content contains the string 'wp:give-wp/services-section-block' or '<!-- wp:give-wp/services-section-block'. Alternatively, use WP-CLI: wp post list --post_type=any --fields=ID,post_title --search='services-section-block'.Affected if Any posts exist that contain the services section block, indicating the vulnerable feature is in use.
-
Inspect post content for the link block attributeExamine the post_content of identified posts. Look for the 'link' attribute within the block JSON, typically appearing as "link":" followed by a URL value. The payload is stored inside HTML comment markers like <!-- and --> surrounding the block markup.Affected if Posts contain the services section block with a 'link' attribute present in the block markup.
-
Search for XSS payload patterns in stored contentUse a database query or WP-CLI to search post_content for suspicious patterns: look for JavaScript: URLs, <script> tags, event handlers like onmouseover/onerror, or encoded payloads within HTML comments near the block data. Example SQL: SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%<!-- wp:give-wp/services-section-block%' AND (post_content LIKE '%javascript:%' OR post_content LIKE '%onerror=%').Affected if Any stored XSS payloads are found in post_content within HTML comments adjacent to the services section block, confirming active exploitation.
You are affected if the Services Section Block plugin is installed at version 1.4.4 or lower AND any posts/pages contain the block with a link attribute that may contain malicious payloads in HTML comments.
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 the latest version when available, as this requires proper input sanitization and output escaping of the link attribute. If no patch is available, remove the plugin until a fix is released.
Version 1.4.5 or latest available version of Services Section Block – Showcase Service Details in Grid or Columns
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Services Section Block – Showcase Service Details in Grid or Columns' plugin
- Check the current version is 1.4.4 or below
- Update the plugin to version 1.4.5 or latest available version
- Verify the update was successful and test that the link functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11402 — 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-11402 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