Skip to main content
CVE-2026-109975VulnerabilityPublished

The Cozy Blocks – Website Builder for WordPress Block Editor | Gutenberg Blocks, Patterns & Templates plugin for

Source GCVE Database

0
Authoritative record:CVE-2026-109975· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 28 Oct 2026, 10:29 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
cozythemesCozy Blocks – Website Builder & Business Growth Toolkit | Popups, Lead Forms & InboxAffected
  • <=2.2.27
Fixed in–

AI-suggested

Users should restrict contributor-level access to trusted users only and consider disabling or removing the Cozy Blocks plugin until a fix is available. Monitor the vendor's advisory channels for updates and patches. Since the vulnerability requires authenticated access, enforcing strict user role management can reduce risk.

Description

The Cozy Blocks plugin for WordPress Block Editor (Gutenberg) versions up to and including 2.2.27 is vulnerable to stored cross-site scripting (XSS) via the 'content' block attribute parameters related to icon.view, icon.layout, and icon.gap. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. This vulnerability arises from insufficient input sanitization and output escaping, as wp_kses_post does not neutralize certain quote-only attribute-breakout payloads lacking '<' characters, leaving exploitable JSON attributes intact at render time.

References

Community reviews

Loading reviews…