GutenKit – Page Builder Blocks, Patterns, and Templates for Gutenberg Block Editor Security & Risk Analysis

The GutenKit Blocks Addon plugin exhibits a mixed security posture. On the positive side, it demonstrates strong practices regarding SQL queries, exclusively using prepared statements, and has a high percentage of properly escaped output. Nonce and capability checks are also present in a reasonable number of entry points. However, a significant concern lies in its attack surface. With 17 REST API routes, a substantial 16 of them lack proper permission callbacks, leaving them unprotected. This is exacerbated by the taint analysis revealing two flows with unsanitized paths, indicating potential avenues for malicious input to be processed without adequate sanitization. The plugin's vulnerability history is also a point of concern. Three known CVEs, including one critical and two medium, have been identified. Although currently unpatched CVEs are zero, the recurring nature of cross-site scripting and missing authorization vulnerabilities suggests underlying architectural weaknesses that need continuous attention. The presence of external HTTP requests, while not inherently a vulnerability, adds to the overall attack surface and requires careful monitoring for any unintended data leakage or supply chain risks. In conclusion, while the plugin shows good practices in areas like SQL and output escaping, the large unprotected attack surface, identified taint flows, and past critical vulnerabilities necessitate a cautious approach.