HomeWordPress vulnerabilitiesBlockArt Blocks
BlockArt Blocks vulnerabilities
BlockArt Blocks has 4 known vulnerabilities in this database. The most recent published record is dated 18 Nov 2026.
- Known vulnerabilities
- 4
- Active installs
- 10,000+
- Latest version
- 2.4.3
- Last updated
- 5 Nov 2026
- Most recent
- 18 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-123343 | Medium 6.5 | Up to 2.4.3 | No fixed version yet | 4 d ago |
| Cross-site scripting (XSS) CVE-2026-3498 | Medium 6.4 | Up to 2.2.15 | Fixed in a later version (latest 2.4.3) | 11 Apr 2026 |
| Cross-site scripting (XSS) CVE-2025-14283 | Medium 6.4 | Up to 2.2.14 | Fixed in a later version (latest 2.4.3) | 28 Jan 2026 |
| Cross-site scripting (XSS) CVE-2025-13697 | Medium 6.4 | Up to 2.2.13 | Fixed in a later version (latest 2.4.3) | 2 Dec 2025 |
Read the published descriptions
- CVE-2026-123343, 18 Nov 2026
- The BlockArt Blocks - Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.4.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to view the title, excerpt, and full content of other users' draft, pending, and private posts, exposing that content to unauthenticated visitors on the published permalink. This is exploitable by an Author-level user because WordPress's wp_filter_post_kses preserves block-comment JSON in HTML comments, allowing the malicious queryArgs and query[post_status] attributes to survive post saving and execute on every unauthenticated request to the published URL. Exploitation by attackers with contributor-level access and above requires that attacker only needs to see the data themselves (not expose it to unauthenticated visitors) - satisfied by viewing their own preview URL. On a default installation, where that is not configured, the vulnerability requires attackers with author-level access and above. CVE record
- CVE-2026-3498, 11 Apr 2026
- The BlockArt Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'clientId' block attribute in all versions up to, and including, 2.2.15. This is 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. CVE record
- CVE-2025-14283, 28 Jan 2026
- The BlockArt Blocks - Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the BlockArt Counter in all versions up to, and including, 2.2.14 due to insufficient input sanitization and output escaping on user supplied attributes. 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. CVE record
- CVE-2025-13697, 2 Dec 2025
- The BlockArt Blocks - Gutenberg Blocks, Page Builder Blocks ,WordPress Block Plugin, Sections & Template Library plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘timestamp’ attribute in all versions up to, and including, 2.2.13 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. CVE record
What to do if you run BlockArt Blocks
If you run BlockArt Blocks, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new BlockArt Blocks vulnerabilities
Free. We email you when a new vulnerability is published for BlockArt Blocks, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.