PatchSiren cyber security CVE debrief
CVE-2026-105890 Liquid Web / StellarWP CVE debrief
The Gutenberg Blocks by Kadence Blocks plugin for WordPress has a Cross Site Scripting (XSS) vulnerability, affecting versions up to 3.7.12. This issue, tracked as CVE-2026-105890, allows for Stored XSS attacks. Defenders should assess exposure and prioritize verification and updates to version 3.7.12.1 or later. The CVE record was published on 2026-10-08T13:02:50.319Z and has not been modified since then. The vendor, Liquid Web / StellarWP, has provided information on the affected version and the fixed version.
- Vendor
- Liquid Web / StellarWP
- Product
- Gutenberg Blocks by Kadence Blocks
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-08
- Original CVE updated
- 2026-10-08
- Advisory published
- 2026-10-08
- Advisory updated
- 2026-10-08
Who should care
Defenders responsible for WordPress environments using the Gutenberg Blocks by Kadence Blocks plugin version <= 3.7.12 should assess exposure and prioritize verification and updates.
Why it matters
Defenders should prioritize verifying and updating the Gutenberg Blocks by Kadence Blocks plugin to version 3.7.12.1 or later, and assess exposure in their WordPress environments due to the Cross Site Scripting (XSS) vulnerability.
- Verification of plugin version and exposure in WordPress environments
- Potential XSS attacks on affected versions
- Prioritization of updates to version 3.7.12.1 or later
Technical summary
The Gutenberg Blocks by Kadence Blocks plugin version <= 3.7.12 has a Cross Site Scripting (XSS) vulnerability. The vendor, Liquid Web / StellarWP, has provided information on the affected version and the fixed version 3.7.12.1. This vulnerability allows for Stored XSS attacks, and defenders should prioritize verifying and updating the plugin to the fixed version. The affected product is used in WordPress environments, and exposure should be assessed and mitigated accordingly. The CVE record provides details on the vulnerability and its impact.
Defensive priority
Defenders should prioritize verifying and updating the Gutenberg Blocks by Kadence Blocks plugin to version 3.7.12.1 or later, and assess exposure in their WordPress environments.
Recommended defensive actions
- Verify and update the Gutenberg Blocks by Kadence Blocks plugin to version 3.7.12.1 or later
- Assess exposure in WordPress environments
- Monitor for potential XSS attacks
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source item provide details on the Cross Site Scripting (XSS) vulnerability in Gutenberg Blocks by Kadence Blocks plugin version <= 3.7.12. The vendor, Liquid Web / StellarWP, has provided information on the affected version and the fixed version 3.7.12.1.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-105890 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-105890
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-105890 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105890
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
WordPress Gutenberg Blocks by Kadence Blocks plugin <= 3.7.12 - Cross Site Scripting (XSS) vulne
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/105xxx/CVE-2026-105890.json
cve_program_cvelist_v5
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.