bCMS Security & Risk Analysis

The "bcms" plugin version 5.3 exhibits a mixed security posture. While the static analysis indicates a relatively small attack surface with all identified entry points seemingly protected by authentication checks (no unprotected AJAX handlers or REST API routes), there are several concerning code signals. The presence of a "unserialize" function without explicit warnings about its use is a significant red flag, as it can lead to serious vulnerabilities if used with untrusted input. Furthermore, a substantial portion of SQL queries are not using prepared statements, increasing the risk of SQL injection. The low percentage of properly escaped output also poses a risk for cross-site scripting (XSS) vulnerabilities.

The plugin's vulnerability history is clean, with no known CVEs. This is a positive indicator, suggesting that the developers have either been diligent in securing the code or that the plugin has not been a significant target. However, the lack of historical vulnerabilities does not negate the risks identified in the static analysis. The strengths lie in the seemingly protected entry points and the absence of known exploits. The weaknesses are primarily in the insecure coding practices identified: the use of unserialize, raw SQL queries, and insufficient output escaping.