Church Admin Security & Risk Analysis

The "church-admin" plugin version 5.0.30 presents a mixed security posture. While it demonstrates good practices in output escaping (89% properly escaped) and utilizes a reasonable number of nonce and capability checks, significant concerns arise from its attack surface and taint analysis. Four of its eight AJAX handlers lack authentication checks, representing a direct pathway for unauthorized actions. The taint analysis is particularly worrying, with 60 high-severity flows and 72 flows with unsanitized paths, indicating a high likelihood of exploitable vulnerabilities in how user-supplied data is handled, even though no critical severity taint flows were detected.

The plugin's vulnerability history is a substantial red flag. With 26 known CVEs, including 5 high-severity ones, and a history of common vulnerability types such as SQL injection, XSS, SSRF, and unauthorized access, it suggests a persistent struggle with secure coding practices. The presence of "unserialize" as a dangerous function, coupled with the high number of unsanitized paths in taint analysis, further amplifies the risk of remote code execution or data breaches. The latest vulnerability listed in 2026 indicates the data might be predictive or historical, but the sheer volume of past issues points to ongoing security weaknesses.

In conclusion, while the plugin has some positive attributes like good output escaping, the high number of unprotected AJAX endpoints, critical taint analysis results, and a long history of diverse and severe vulnerabilities collectively paint a picture of a high-risk plugin. The prevalence of past vulnerabilities suggests that even with current efforts, the underlying codebase may contain recurring security flaws. It is strongly recommended that users exercise extreme caution and prioritize updating to a version with thoroughly addressed and verified security fixes.