OrendaPay Security & Risk Analysis

The orendapay v4.3.1 plugin exhibits a mixed security posture. On the positive side, there are no recorded vulnerabilities (CVEs) and the plugin does not appear to use dangerous functions. All SQL queries are correctly prepared, which is a strong security practice. However, significant concerns arise from the static analysis. A concerningly low 8% of output is properly escaped, leaving potential for cross-site scripting (XSS) vulnerabilities. The presence of file operations and external HTTP requests without apparent authorization checks or sanitization on paths is a notable risk, as indicated by the taint analysis showing all flows with unsanitized paths. Furthermore, the complete lack of nonce and capability checks on entry points is a critical oversight, especially given the presence of file operations and external requests that could be triggered by unauthenticated users.