SEMA API Security & Risk Analysis

The sema-api v6.22 plugin exhibits a mixed security posture. While it demonstrates good practices in SQL query preparation (98%) and a majority of output escaping (78%), several significant concerns are present. The presence of two unprotected AJAX handlers creates a substantial attack surface, potentially allowing unauthenticated users to trigger plugin functionality. Taint analysis reveals six high-severity flows with unsanitized paths, indicating potential vulnerabilities where user input could be manipulated to achieve unintended or malicious outcomes, even though no critical severity flows were found.

The plugin's vulnerability history, with two known CVEs including one critical and one medium, both related to Cross-Site Scripting and SQL Injection, is concerning. While there are currently no unpatched vulnerabilities, the recurring nature of these vulnerability types suggests a pattern of inadequate input sanitization and output escaping, particularly for specific input vectors. The last vulnerability being recent further underscores the need for vigilance.

In conclusion, sema-api v6.22 has some strengths in its handling of database interactions. However, the unprotected entry points, high-severity taint flows, and past critical vulnerabilities necessitate careful consideration. The plugin's security would be significantly improved by addressing the unprotected AJAX handlers and thoroughly reviewing and sanitizing all user-influenced data flows identified by the taint analysis, especially in light of its historical vulnerabilities.