pensopay Payments Security & Risk Analysis

The "woo-pensopay" plugin version 7.1.9 presents a mixed security posture. While the static analysis shows no critical or high severity taint flows and a lack of dangerous functions, several areas raise significant concerns. A substantial portion of the attack surface, specifically 5 out of 7 AJAX handlers and 1 REST API route, lack proper authentication or permission checks. This opens the door to unauthorized actions and potential privilege escalation if malicious input can be supplied. Furthermore, all SQL queries are executed without prepared statements, a practice that significantly increases the risk of SQL injection vulnerabilities. The output escaping is also a concern, with only 29% of outputs being properly sanitized, indicating a high risk of Cross-Site Scripting (XSS) vulnerabilities.

The plugin's vulnerability history, including a medium severity CVE related to XSS, reinforces the concerns about improper input handling and output sanitization. While there are no currently unpatched vulnerabilities, the past occurrence of XSS suggests a recurring pattern of insecure coding practices. The presence of nonce checks and capability checks indicates some awareness of security, but their limited implementation leaves many entry points vulnerable. The plugin's strengths lie in its clean code regarding dangerous functions and taint analysis, but these are overshadowed by the numerous unprotected entry points and the critical lack of prepared statements for SQL queries, making it a moderate to high risk.