HomeWordPress vulnerabilitiesPage Builder Gutenberg Blocks
Page Builder Gutenberg Blocks vulnerabilities
Page Builder Gutenberg Blocks has 6 known vulnerabilities in this database. The most recent published record is dated 18 Apr 2026.
- Known vulnerabilities
- 6
- Active installs
- 300,000+
- Latest version
- 3.1.17
- Last updated
- 5 Mar 2026
- Most recent
- 18 Apr 2026
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 |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-4801 | Medium 6.4 | Up to 3.1.16 | Fixed in a later version (latest 3.1.17) | 18 Apr 2026 |
| Cross-site scripting (XSS) CVE-2024-7132 | Medium 4.8 | Before 3.1.13 | Fixed in 3.1.13 | 29 Aug 2024 |
| Server-side request forgery (SSRF) CVE-2024-4260 | Medium 6.5 | Before 3.1.12 | Fixed in 3.1.12 | 23 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-2933 | Medium 6.4 | Up to 3.1.9 | Fixed in a later version (latest 3.1.17) | 1 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-2369 | Medium 5.4 | Before 3.1.7 | Fixed in 3.1.7 | 2 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-1049 | Medium 6.4 | Up to 3.1.6 | Fixed in a later version (latest 3.1.17) | 23 Mar 2024 |
Read the published descriptions
- CVE-2026-4801, 18 Apr 2026
- The Page Builder Gutenberg Blocks - CoBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via external iCal feed data in all versions up to, and including, 3.1.16 due to insufficient output escaping of event titles, descriptions, and locations fetched from external iCal feeds in the Events block rendering function. 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-2024-7132, 29 Aug 2024
- The Page Builder Gutenberg Blocks WordPress plugin before 3.1.13 does not escape the content of post embed via one of its block, which could allow users with the capability to publish posts (editor and admin by default) to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-4260, 23 Jul 2024
- The Page Builder Gutenberg Blocks WordPress plugin before 3.1.12 does not prevent users from pinging arbitrary hosts via some of its shortcodes, which could allow high privilege users such as contributors to perform SSRF attacks. CVE record
- CVE-2024-2933, 1 Jun 2024
- The Page Builder Gutenberg Blocks - CoBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Social Profiles widget in all versions up to, and including, 3.1.9 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-2024-2369, 2 Apr 2024
- The Page Builder Gutenberg Blocks WordPress plugin before 3.1.7 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks CVE record
- CVE-2024-1049, 23 Mar 2024
- The Page Builder Gutenberg Blocks - CoBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Icon Widget's in all versions up to, and including, 3.1.6 due to insufficient input sanitization and output escaping on the link value. This makes it possible for authenticated attackers with contributor-level and above permissions 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 Page Builder Gutenberg Blocks
If you run Page Builder Gutenberg 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 Page Builder Gutenberg Blocks vulnerabilities
Free. We email you when a new vulnerability is published for Page Builder Gutenberg 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.