FormGlut — Contact, Newsletter & Multi-step Form Builder Security & Risk Analysis

The "formglut" plugin v1.1.2 presents a concerning security posture due to a significant attack surface without adequate authentication. All six identified AJAX handlers lack authorization checks, meaning any authenticated user could potentially trigger these functions, leading to unintended actions or data manipulation. While the plugin shows good practices in SQL query preparation and output escaping, the absence of nonce checks on these critical AJAX entry points is a major oversight that could facilitate CSRF attacks.

The presence of the `unserialize` function, especially without clear sanitization or validation of the input being unserialized, is a high-risk indicator. Although the taint analysis did not reveal critical or high-severity flows with unsanitized paths in this specific analysis run, the potential for deserialization vulnerabilities remains a significant concern. The plugin's history of zero known CVEs and no recorded vulnerabilities is a positive sign, suggesting either a lack of past exploitation or a history of secure development. However, this cannot negate the immediate risks identified in the static analysis.

In conclusion, while "formglut" demonstrates some good security practices regarding database queries and output handling, the unprotected AJAX endpoints and the use of `unserialize` create substantial security weaknesses. The lack of vulnerability history should not be interpreted as a guarantee of current security, especially given the identified code signals and attack surface. These issues require immediate attention to mitigate potential exploitation.