bpost-shipping-platform Security & Risk Analysis

The bpost-shipping-platform plugin v3.2.2 presents a mixed security posture. On the positive side, the plugin demonstrates good practices in several areas. The vast majority of SQL queries utilize prepared statements, and output escaping is robust, with almost all outputs being properly escaped. The absence of dangerous functions and a clean vulnerability history with no recorded CVEs suggest a generally well-maintained codebase. However, significant security concerns arise from its attack surface. A substantial number of AJAX handlers (12 out of 17) and all REST API routes lack proper authentication or permission checks. This creates a considerable attack vector where unauthenticated users could potentially interact with sensitive functionalities. Furthermore, two taint analysis flows were found with unsanitized paths, indicating a potential for path traversal vulnerabilities, even though they are not currently classified as critical or high severity. The lack of capability checks and the limited number of nonce checks on entry points exacerbate these risks. While the plugin has no known CVEs, the uncovered vulnerabilities in its attack surface could be exploited by attackers, especially given the high number of unprotected entry points.