Church Data Connect for Church Community Builder Security & Risk Analysis

The "ccbpress-core" v1.5.1 plugin exhibits a concerning security posture primarily due to a significantly exposed attack surface without proper authentication. All 11 identified REST API routes lack permission callbacks, meaning any unauthenticated user can potentially interact with these endpoints, leading to a high risk of unauthorized access or manipulation of plugin functionalities. While the plugin demonstrates good practices in SQL query handling (100% prepared statements) and has a clean vulnerability history with no recorded CVEs, these strengths are heavily overshadowed by the lack of authorization on its entry points. The absence of capability checks further exacerbates this issue, as there are no backend controls to verify user roles and permissions for these exposed routes. The static analysis also revealed a moderate concern with output escaping, where 22% of outputs are not properly escaped, potentially opening the door for cross-site scripting (XSS) vulnerabilities, although no critical or high severity taint flows were detected. The presence of only two nonce checks is also insufficient given the number of potential entry points. The plugin's strengths lie in its secure SQL practices and clean vulnerability record, but the significant lack of authentication and authorization on its REST API routes presents a critical weakness that demands immediate attention.