HomeWordPress vulnerabilitiesGutenBee
GutenBee vulnerabilities
GutenBee has 2 known vulnerabilities in this database. The most recent published record is dated 28 May 2026.
- Known vulnerabilities
- 2
- Active installs
- 6,000+
- Latest version
- 2.20.3
- Last updated
- 27 May 2026
- Most recent
- 28 May 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 |
|---|---|---|---|---|
| Remote code execution CVE-2026-9227 | High 8.8 | Up to 2.20.1 | Fixed in a later version (latest 2.20.3) | 28 May 2026 |
| Cross-site scripting (XSS) CVE-2025-8566 | Medium 6.4 | Up to 2.18.0 | Fixed in a later version (latest 2.20.3) | 30 Sep 2025 |
Read the published descriptions
- CVE-2026-9227, 28 May 2026
- The GutenBee - Gutenberg Blocks plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 2.20.1 via the gutenbee_file_and_ext_json function. This is due to a flawed strpos() substring check that only verifies whether the filename contains the string '.json' rather than confirming the filename ends with a .json extension, allowing double-extension filenames like shell.json.php to bypass validation. This makes it possible for authenticated attackers, with author-level access and above, to upload files that may be executable, which makes remote code execution possible. CVE record
- CVE-2025-8566, 30 Sep 2025
- The GutenBee - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via parameters in the CountUp and Google Maps Blocks in all versions up to, and including, 2.18.0 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
What to do if you run GutenBee
If you run GutenBee, 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 GutenBee vulnerabilities
Free. We email you when a new vulnerability is published for GutenBee, 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.