Findings

CVE-2026-6378

The Maxi Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API endpoint in all versions up to, and including, 2.1.9 due to insuffic…

Published May 2, 2026 · updated Jun 17, 2026

The Maxi Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API endpoint in all versions up to, and including, 2.1.9 due to insufficient input sanitization and output escaping of the parameter. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts that execute on every page where the plugin's style card styles are loaded, including across the entire WordPress admin panel.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 2, 2026 · NIST NVD

    Detected

    The Maxi Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API endpoint in all versions up to, and including, 2.1.9 due to insufficient input sanitization and output escaping of the parameter. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts that execute on every page where the plugin's style

  2. Jun 17, 2026 · NIST NVD

    Updated

    The Maxi Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API endpoint in all versions up to, and including, 2.1.9 due to insufficient input sanitization and output escaping of the parameter. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts that execute on every page where the plugin's style

Sources

  • CVE.orgVulnerability recordCVE-2026-6378

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-6378

    The Maxi Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API endpoint in all versions up to, and including, 2.1.9 due to insufficient input sanitization and output escaping of the parameter.

    nvd.nist.gov

References