Page Builder Gutenberg Blocks at a glance
- 7 publicly disclosed vulnerabilities. The most recent was disclosed on Apr 17, 2026.
- Ranked #181 by popularity on WordPress.org (300,000+ active installs).
- The latest version is 3.1.17 (released Mar 5, 2026). The most recent security fix shipped in 3.1.17.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Page Builder Gutenberg Blocks version
Enter the Page Builder Gutenberg Blocks version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Page Builder Gutenberg Blocks”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Page Builder Gutenberg Blocks”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.1.17). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Page Builder Gutenberg Blocks vulnerabilities
Page Builder Gutenberg Blocks <= 3.1.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via External iCal Feed Data
Cross-site scripting (XSS) · CVE-2026-4801
Affected versions: ≤ 3.1.16
Fixed in: 3.1.17
Severity: Medium 6.4 · Disclosed Apr 17, 2026
Page Builder Gutenberg Blocks – CoBlocks <= 3.1.16 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-27094
Affected versions: ≤ 3.1.16
Fixed in: 3.1.17
Severity: Medium 6.4 · Disclosed Jan 7, 2026
CoBlocks <= 3.1.13 - Missing Authorization
Missing authorization · CVE-2025-24751
Affected versions: ≤ 3.1.13
Fixed in: 3.1.14
Severity: Medium 4.3 · Disclosed Jan 24, 2025
Page Builder Gutenberg Blocks – CoBlocks <= 3.1.12 - Authenticated (Editor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-7132
Affected versions: ≤ 3.1.12
Fixed in: 3.1.13
Severity: Medium 4.4 · Disclosed Aug 8, 2024
Page Builder Gutenberg Blocks – CoBlocks <= 3.1.11 - Authenticated (Contributor+) Server-Side Request Forgery
Server-side request forgery (SSRF) · CVE-2024-4260
Affected versions: ≤ 3.1.11
Fixed in: 3.1.12
Severity: Medium 4.3 · Disclosed Jul 2, 2024
Page Builder Gutenberg Blocks – CoBlocks <= 3.1.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Social Profiles
Cross-site scripting (XSS) · CVE-2024-2933
Affected versions: ≤ 3.1.9
Fixed in: 3.1.10
Severity: Medium 6.4 · Disclosed May 31, 2024
Page Builder Gutenberg Blocks – CoBlocks <= 3.1.6 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-1049
Affected versions: ≤ 3.1.6
Fixed in: 3.1.7
Severity: Medium 6.4 · Disclosed Mar 12, 2024
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Page Builder Gutenberg Blocks <= 3.1.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via External iCal Feed DataCross-site scripting (XSS) · CVE-2026-4801 | ≤ 3.1.16 | 3.1.17 | Medium 6.4 | Apr 17, 2026 |
| Page Builder Gutenberg Blocks – CoBlocks <= 3.1.16 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-27094 | ≤ 3.1.16 | 3.1.17 | Medium 6.4 | Jan 7, 2026 |
| CoBlocks <= 3.1.13 - Missing AuthorizationMissing authorization · CVE-2025-24751 | ≤ 3.1.13 | 3.1.14 | Medium 4.3 | Jan 24, 2025 |
| Page Builder Gutenberg Blocks – CoBlocks <= 3.1.12 - Authenticated (Editor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-7132 | ≤ 3.1.12 | 3.1.13 | Medium 4.4 | Aug 8, 2024 |
| Page Builder Gutenberg Blocks – CoBlocks <= 3.1.11 - Authenticated (Contributor+) Server-Side Request ForgeryServer-side request forgery (SSRF) · CVE-2024-4260 | ≤ 3.1.11 | 3.1.12 | Medium 4.3 | Jul 2, 2024 |
| Page Builder Gutenberg Blocks – CoBlocks <= 3.1.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Social ProfilesCross-site scripting (XSS) · CVE-2024-2933 | ≤ 3.1.9 | 3.1.10 | Medium 6.4 | May 31, 2024 |
| Page Builder Gutenberg Blocks – CoBlocks <= 3.1.6 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-1049 | ≤ 3.1.6 | 3.1.7 | Medium 6.4 | Mar 12, 2024 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Apr 17, 2026.
Most common weaknesses in Page Builder Gutenberg Blocks
Cross-site scripting (XSS)
5 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
1 issue
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Server-side request forgery (SSRF)
1 issue
Your server can be made to send requests to other systems on the attacker’s behalf, including internal ones.
Frequently asked questions
Is Page Builder Gutenberg Blocks safe to use?
Page Builder Gutenberg Blocks is a well-known plugin with 300,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.1.17) and turn on automatic updates.
How do I find which version of Page Builder Gutenberg Blocks my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesPage Builder Gutenberg Blocks on WordPress.org