CVE-2026-6740
MediumCVSS 6.4Exploitation Probability (EPSS)
Low risk5th percentile - higher than 5% of all known CVEs
Summary
The Nexter Blocks plugin for WordPress up to version 4.7.4 is vulnerable to Stored Cross-Site Scripting via the 'commentIcon' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with contributor-level access or higher can inject arbitrary scripts that execute when a user visits an affected page.
Risk Assessment
An attacker can inject malicious JavaScript, leading to session theft, redirects to malicious sites, or website defacement, compromising visitor security and organizational reputation.
Recommendation
Immediately update the Nexter Blocks plugin to the latest available version that fixes this vulnerability. If no update is available, temporarily disable the plugin or restrict user permissions below contributor level.
Other vulnerabilities in Nexter Blocks
See all- CVE-2025-15678Medium
The Nexter Blocks WordPress plugin before version 5.0.2 does not sanitize uploaded SVG files and allows SVG uploads for any user able to upload files (Author by default). This allows them to upload a file containing malicious JavaScript that executes when the file is accessed, leading to Stored Cross-Site Scripting.
- CVE-2026-15420Medium
The Nexter Blocks plugin for WordPress up to version 5.0.0 has a directory traversal vulnerability via the 'plus_name' parameter. Authenticated attackers with subscriber-level access or higher can delete arbitrary JS/CSS files on the server.
- CVE-2026-39516Medium
The Nexter Blocks WordPress plugin exposes sensitive system information to unauthorized entities. The vulnerability allows retrieval of embedded sensitive data.
Original NVD description (English source)
The Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'commentIcon' parameter in all versions up to, and including, 4.7.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.