Sign Customiser Security & Risk Analysis

The "sign-customiser" plugin v1.6.2 exhibits a mixed security posture. While it demonstrates good practices by avoiding dangerous functions and using prepared statements for all SQL queries, and importantly, has no recorded vulnerability history, several critical concerns are present.

The static analysis reveals a significant attack surface with one unprotected REST API route. Furthermore, only 30% of output is properly escaped, and there are no nonce or capability checks implemented for any entry points. The presence of file operations and external HTTP requests without apparent sanitization or validation in the analyzed code signals potential avenues for exploitation.

Despite the absence of past CVEs, the current lack of robust authentication and authorization checks on its entry points, combined with insufficient output escaping, creates a substantial risk. The plugin's strengths in SQL handling and lack of historical vulnerabilities are overshadowed by the immediate threats posed by its unprotected REST API route and general lack of input validation and output sanitization.