HomeWordPress vulnerabilitiesGutenKit
GutenKit vulnerabilities
GutenKit has 6 known vulnerabilities in this database. The most recent published record is dated 3 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 80,000+
- Latest version
- 2.5.2
- Last updated
- 27 Sep 2026
- Most recent
- 3 Sep 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-2573 | Medium 6.4 | Up to 2.4.4 | Fixed in a later version (latest 2.5.2) | 3 Sep 2026 |
| Security weakness CVE-2026-19698 | Low 3.5 | Before 2.5.1 | Fixed in 2.5.1 | 2 Sep 2026 |
| Broken access control CVE-2026-19699 | Low 2.7 | Before 2.5.0 | Fixed in 2.5.0 | 20 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-19697 | Medium 6.8 | Before 2.5.0 | Fixed in 2.5.0 | 20 Aug 2026 |
| Broken access control CVE-2026-15827 | Medium 5.3 | Up to 2.4.12 | Fixed in a later version (latest 2.5.2) | 23 Jul 2026 |
| Arbitrary file upload CVE-2024-9234 | Critical 9.8 | Up to 2.1.0 | Fixed in a later version (latest 2.5.2) | 11 Oct 2024 |
Read the published descriptions
- CVE-2026-2573, 3 Sep 2026
- The GutenKit - Page Builder Blocks, Patterns, and Templates for Gutenberg Block Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘postBodyCss’ parameter in all versions up to, and including, 2.4.4 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
- CVE-2026-19698, 2 Sep 2026
- The GutenKit WordPress plugin before 2.5.1 does not validate or escape style settings saved against a post before using them to build the CSS it outputs on the front end, allowing users with the Contributor role and above to inject arbitrary CSS into pages served to other users and to anonymous visitors. JavaScript execution is not possible at that role, so the impact is limited to defacement, interface redressing and forcing external resources to load. CVE record
- CVE-2026-19699, 20 Aug 2026
- The GutenKit WordPress plugin before 2.5.0 does not have a sufficient capability check on some of its REST API endpoints, allowing users with the Contributor role and above to retrieve mailing-list audience metadata from the site's connected marketing account. CVE record
- CVE-2026-19697, 20 Aug 2026
- The GutenKit WordPress plugin before 2.5.0 does not sanitise uploaded SVG files on all of the upload paths it enables, allowing users with the file upload capability, such as Author, to upload a malicious SVG and perform Stored Cross-Site Scripting attacks against any user opening it, including administrators. CVE record
- CVE-2026-15827, 23 Jul 2026
- The GutenKit Blocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/gutenkit/v1/mailchimp/get/lists and /wp-json/gutenkit/v1/mailchimp/get/interests REST API endpoints in versions up to, and including, 2.4.12. Both endpoints are registered with permission_callback => '__return_true', and their callbacks read the site's stored Mailchimp API key from the gutenkit_settings_list option and proxy Mailchimp audience/list, merge-field, interest-category, interest-name, and subscriber-count metadata back to the caller with no login, nonce, or capability check. This makes it possible for unauthenticated attackers to retrieve private Mailchimp audience configuration information from any site that has configured the GutenKit Mailchimp integration. CVE record
- CVE-2024-9234, 11 Oct 2024
- The GutenKit - Page Builder Blocks, Patterns, and Templates for Gutenberg Block Editor plugin for WordPress is vulnerable to arbitrary file uploads due to a missing capability check on the install_and_activate_plugin_from_external() function (install-active-plugin REST API endpoint) in all versions up to, and including, 2.1.0. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins, or utilize the functionality to upload arbitrary files spoofed like plugins. CVE record
What to do if you run GutenKit
If you run GutenKit, 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 GutenKit vulnerabilities
Free. We email you when a new vulnerability is published for GutenKit, 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.