Getwid – Gutenberg Blocks Security & Risk Analysis

The Getwid plugin exhibits a mixed security posture. While a high percentage of its output is properly escaped and it shows a good number of capability checks and nonces, there are significant areas of concern. The presence of two AJAX handlers without authentication checks presents a direct attack vector. Furthermore, the plugin's history of 11 known CVEs, including a high-severity one in the past, suggests a pattern of vulnerabilities that require careful monitoring. The types of past vulnerabilities, such as Cross-Site Scripting, Missing Authorization, and SSRF, are particularly worrying as they can lead to severe compromises.

The static analysis reveals a substantial attack surface with 8 AJAX handlers, two of which lack necessary authorization checks. The single SQL query identified is not using prepared statements, increasing the risk of SQL injection. Although taint analysis did not reveal critical or high severity unsanitized paths, one flow with unsanitized paths is still a concern, especially in conjunction with the history of XSS vulnerabilities. The bundled Lodash library, if outdated, could also pose a risk, though its specific version is not provided.

In conclusion, while Getwid demonstrates some good security practices like proper output escaping and a good number of capability checks, the unauthenticated AJAX endpoints and the plugin's history of numerous vulnerabilities, including a high-severity one, cannot be overlooked. The lack of prepared statements for its SQL query is another point of concern. Users should exercise caution and ensure the plugin is updated to the latest version to mitigate known risks.