HomeWordPress vulnerabilitiesGutenberg Block Editor Toolkit
Gutenberg Block Editor Toolkit vulnerabilities
Gutenberg Block Editor Toolkit has 3 known vulnerabilities in this database. The most recent published record is dated 30 Mar 2024.
- Known vulnerabilities
- 3
- Active installs
- 20,000+
- Latest version
- 1.40.6
- Last updated
- 28 May 2024
- Most recent
- 30 Mar 2024
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-2024-2794 | Medium 6.4 | Up to 1.40.4 | Fixed in a later version (latest 1.40.6) | 30 Mar 2024 |
| Remote code execution CVE-2023-6635 | High 7.2 | Up to 1.40.3 | Fixed in a later version (latest 1.40.6) | 5 Feb 2024 |
| Remote code execution CVE-2021-24546 | High 8.8 | Before 1.31.6 | Fixed in 1.31.6 | 11 Oct 2021 |
Read the published descriptions
- CVE-2024-2794, 30 Mar 2024
- The Gutenberg Block Editor Toolkit - EditorsKit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'editorskit' shortcode in all versions up to, and including, 1.40.4 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-2024-32586 is likely a duplicate of this issue. CVE record
- CVE-2023-6635, 5 Feb 2024
- The EditorsKit plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation on the 'import_styles' function in versions up to, and including, 1.40.3. This makes it possible for authenticated attackers with administrator-level capabilities or above, to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2021-24546, 11 Oct 2021
- The Gutenberg Block Editor Toolkit - EditorsKit WordPress plugin before 1.31.6 does not sanitise and validate the Conditional Logic of the Custom Visibility settings, allowing users with a role as low contributor to execute Arbitrary PHP code CVE record
What to do if you run Gutenberg Block Editor Toolkit
If you run Gutenberg Block Editor Toolkit, 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 Gutenberg Block Editor Toolkit vulnerabilities
Free. We email you when a new vulnerability is published for Gutenberg Block Editor Toolkit, 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.