Another Unit Converter Security & Risk Analysis

The plugin "another-unit-converter" v1.1.2 exhibits a concerning security posture primarily due to its extensive unprotected attack surface. All 11 identified AJAX handlers lack authentication checks, presenting a significant risk of unauthorized execution of plugin functions. While the code shows positive signs like 100% usage of prepared statements for SQL queries and no recorded vulnerabilities in its history, the absence of basic security measures on entry points overshadows these strengths.

The lack of proper output escaping on a substantial portion (62%) of outputs is another area of concern, potentially leading to cross-site scripting (XSS) vulnerabilities if user-supplied data is not handled carefully. Although taint analysis shows no identified flows, this is likely due to the limited scope of the analysis or the plugin's relatively simple functionality. The absence of nonce checks on AJAX handlers is a critical oversight, making it susceptible to CSRF attacks. The singular capability check on one entry point is insufficient given the number of unprotected handlers.

In conclusion, while the plugin benefits from clean SQL practices and a clean vulnerability history, the significant number of unprotected AJAX endpoints and the high percentage of unescaped output are critical weaknesses. These issues create a substantial attack surface that could be exploited by malicious actors. Addressing the lack of authentication and proper output sanitization on all entry points should be a top priority to improve the plugin's security.