CVE-2026-9227: GutenBee (WordPress plugin) · Unrestricted File Upload
Affects GutenBee (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| cssigniterteamGutenBee – Gutenberg Blocks | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict author-level user permissions carefully and monitor for suspicious file uploads. Avoid granting author-level access to untrusted users. Consider disabling or replacing the GutenBee plugin if possible to mitigate risk.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/2d20e8c9-975d-4e8c-8bea-50935853c7d4?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.1/gutenbee.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.1/gutenbee.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.1/gutenbee.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.0/gutenbee.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.0/gutenbee.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/gutenbee/tags/2.20.0/gutenbee.php (opens in a new tab)
- github.com/cssigniter/gutenbee/commit/bde934cdecf67a4de1d6548cc1fc6c59bc6690e5 (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3543574%40gutenbee&new=3543574%40gutenbee&sfp_email=&sfph_mail= (opens in a new tab)