LoginWP (Formerly Peter's Login Redirect) Security & Risk Analysis

The 'peters-login-redirect' plugin, version 3.0.8.8, presents a mixed security posture. While the static analysis shows a good number of defensive measures like nonce and capability checks, the output escaping is a significant concern, with only 48% of outputs being properly escaped. This could leave the plugin vulnerable to Cross-Site Scripting (XSS) attacks if user-supplied data is not handled with sufficient care. The SQL query preparedness is also not ideal, with 45% of queries not using prepared statements, which could introduce SQL injection risks. The plugin's vulnerability history is notable, with 3 past CVEs, including one high severity XSS and two medium severity vulnerabilities. The absence of currently unpatched vulnerabilities is positive, but the recurring nature of XSS and CSRF in its history suggests a pattern of input validation and output sanitization weaknesses that have been exploited previously.

Despite the presence of many security checks, the code signals for output escaping and SQL query preparedness raise red flags. The attack surface is primarily composed of AJAX handlers, all of which appear to have authentication checks, which is a positive sign. However, the lack of robust sanitization and escaping mechanisms creates potential entry points for attackers. The vulnerability history further reinforces the need for caution, as past issues point to fundamental security flaws that may not be entirely resolved in this version. Overall, while the plugin attempts to implement security controls, the identified weaknesses in output sanitization and SQL practices, combined with its vulnerability history, indicate a moderate to high risk of exploitation.