2Checkout Integration for WordPress – WP Super Pay Security & Risk Analysis

The 2Checkout plugin v1.0 exhibits a mixed security posture. While it boasts a seemingly small attack surface with no unprotected entry points like AJAX handlers, REST API routes, or shortcodes, and no publicly disclosed vulnerabilities (CVEs), significant concerns arise from the static code analysis. The presence of the dangerous `unserialize` function, coupled with two taint flows identified with unsanitized paths, indicates a high risk of deserialization vulnerabilities. These can lead to remote code execution if an attacker can control the data being unserialized. Furthermore, the absence of nonce checks and capability checks is alarming, as these are fundamental WordPress security mechanisms to prevent Cross-Site Request Forgery (CSRF) and unauthorized actions. The fact that 60% of SQL queries are not using prepared statements also presents a risk of SQL injection. Despite the lack of historical CVEs, the internal code signals suggest a plugin that requires immediate attention to address these inherent security weaknesses before they can be exploited.