Gutenberg at a glance
- 6 publicly disclosed vulnerabilities. The most recent was disclosed on Oct 25, 2025.
- Ranked #145 by popularity on WordPress.org (400,000+ active installs).
- The latest version is 24.4.2 (released Nov 18, 2026). The most recent security fix shipped in 21.9.0.
- 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 Gutenberg version
Enter the Gutenberg 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 “Gutenberg”, 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 “Gutenberg”.
- 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 (24.4.2). 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 Gutenberg vulnerabilities
Gutenberg <= 21.8.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2025-64354
Affected versions: ≤ 21.8.2
Fixed in: 21.9.0
Severity: Medium 6.4 · Disclosed Oct 25, 2025
WordPress Core < 6.5.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via Template Part Block
Cross-site scripting (XSS) · CVE-2024-31111
Affected versions: ≤ 18.6.0
Fixed in: 18.6.1
Severity: Medium 6.4 · Disclosed Jun 24, 2024
Gutenberg 12.9.0 - 18.0.0 - Unauthenticated & Authenticated (Contributor+) Stored Cross-Site Scripting via Avatar Block
Cross-site scripting (XSS)
Affected versions: ≥ 12.9.0, ≤ 18.0.0
Fixed in: 18.01
Severity: Medium 6.4 · Disclosed Apr 9, 2024
WordPress Core 5.9-6.3.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via Navigation Attributes
Cross-site scripting (XSS) · CVE-2023-38000
Affected versions: ≤ 16.8.0
Fixed in: 16.8.1
Severity: Medium 6.4 · Disclosed Oct 12, 2023
WordPress Core < 6.0.3 & Gutenberg < 14.3.1 - Authenticated Cross-Site Scripting in Various Blocks
Cross-site scripting (XSS) · CVE-2022-43500
Affected versions: ≤ 14.3.0
Fixed in: 14.3.1
Severity: Medium 6.4 · Disclosed Oct 18, 2022
WordPress Core < 5.9.2 & Gutenberg < 12.7.2 - Prototype Pollution via Block Editor
Other weakness
Affected versions: < 12.7.2
Fixed in: 12.7.2
Severity: Medium 5.4 · Disclosed Mar 11, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Gutenberg <= 21.8.2 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2025-64354 | ≤ 21.8.2 | 21.9.0 | Medium 6.4 | Oct 25, 2025 |
| WordPress Core < 6.5.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via Template Part BlockCross-site scripting (XSS) · CVE-2024-31111 | ≤ 18.6.0 | 18.6.1 | Medium 6.4 | Jun 24, 2024 |
| Gutenberg 12.9.0 - 18.0.0 - Unauthenticated & Authenticated (Contributor+) Stored Cross-Site Scripting via Avatar BlockCross-site scripting (XSS) | ≥ 12.9.0, ≤ 18.0.0 | 18.01 | Medium 6.4 | Apr 9, 2024 |
| WordPress Core 5.9-6.3.1 - Authenticated(Contributor+) Stored Cross-Site Scripting via Navigation AttributesCross-site scripting (XSS) · CVE-2023-38000 | ≤ 16.8.0 | 16.8.1 | Medium 6.4 | Oct 12, 2023 |
| WordPress Core < 6.0.3 & Gutenberg < 14.3.1 - Authenticated Cross-Site Scripting in Various BlocksCross-site scripting (XSS) · CVE-2022-43500 | ≤ 14.3.0 | 14.3.1 | Medium 6.4 | Oct 18, 2022 |
| WordPress Core < 5.9.2 & Gutenberg < 12.7.2 - Prototype Pollution via Block EditorOther weakness | < 12.7.2 | 12.7.2 | Medium 5.4 | Mar 11, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 25, 2025.
Most common weaknesses in Gutenberg
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.
Frequently asked questions
Is Gutenberg safe to use?
Gutenberg is a well-known plugin with 400,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 (24.4.2) and turn on automatic updates.
How do I find which version of Gutenberg 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.