GB Forms DB Security & Risk Analysis

The gb-forms-db plugin version 1.0.4 presents a mixed security posture. On the positive side, it demonstrates good practices with a significant majority of output being properly escaped and includes nonce checks for its entry points. The attack surface for direct user interaction via AJAX and shortcodes is relatively small and, crucially, appears to be protected by authentication checks, as indicated by zero unprotected entry points.

However, there are notable concerns. The static analysis reveals that 100% of its SQL queries are not using prepared statements, which represents a significant risk for SQL injection vulnerabilities, especially if user-supplied data is ever incorporated into these queries. Furthermore, the presence of two flows with unsanitized paths in the taint analysis, even if not reaching critical or high severity in this specific scan, indicates potential for path traversal or similar issues if not handled carefully.

The plugin's vulnerability history is a major red flag. It has a history of critical vulnerabilities, specifically an 'Improper Control of Generation of Code' (Code Injection) type. While there are no currently unpatched vulnerabilities, the existence of a past critical CVE, especially one related to code injection, suggests that the codebase may have underlying architectural weaknesses that could be exploited in the future, even with seemingly good practices in other areas. The last vulnerability was also very recent, highlighting a pattern of security issues.