Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-9227

CVE-2026-9227 - Gutenbee Plugin

CVE-2026-9227

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-2026-9227

HIGH CVSS 8.8 Published 2026-05-28 Updated 2026-05-28
AI Risk Critical (100/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P1 Immediate
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Components 2
Reference Links 9
AI Risk Engine Critical (100/100)
Exploitability High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2026-05-28 CVE published and first recorded in the threat feed.
  2. 2026-05-28 Record updated with latest vulnerability metadata.
  3. 2026-05-28 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 2 days ago

AI enriched 2 days ago (2026-05-28 21:19 UTC)

Technical Summary

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…

Potential Impact

Severity is HIGH (CVSS 8.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, remote code execution potential.

Primary risk drivers: published exploit references, remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 100/100 (Critical, High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Gutenbee PLUGIN · gutenbee Affected: >= 0, <= 2.20.1 Fixed version not specified
Gutenberg Blocks PLUGIN · gutenberg-blocks Affected: >= 0, <= 2.20.1 Fixed version not specified

References

Scroll to top