Leyka Security & Risk Analysis

The "leyka" v3.32.1 plugin presents a mixed security posture. On the positive side, it demonstrates good practices in SQL query handling, with 73% using prepared statements, and a strong adherence to output escaping, with 98% of outputs properly sanitized. The presence of numerous nonce and capability checks (37 and 20 respectively) also indicates an effort to secure functionalities.

However, significant concerns arise from the attack surface and the plugin's vulnerability history. The plugin exposes 12 unprotected AJAX handlers, creating a substantial entry point for potential unauthorized actions or information disclosure. While taint analysis shows no critical or high severity flows, the 17 flows with unsanitized paths warrant further investigation. The plugin's history of 12 known CVEs, with 2 currently unpatched and including critical and high severity issues such as Remote File Inclusion and Authorization Bypass, is a major red flag. The prevalence of these vulnerability types suggests systemic weaknesses in how user inputs are handled and access controls are implemented.

In conclusion, while "leyka" v3.32.1 exhibits some good security practices, the high number of known, and particularly unpatched, vulnerabilities, coupled with a notable attack surface without authentication, makes it a high-risk plugin. The recurring patterns of severe vulnerability types suggest ongoing development or maintenance issues that need to be addressed proactively.