Table of content Security & Risk Analysis

The "content-table" plugin version 1.5.3.1 presents a significant security risk due to a combination of poor coding practices and a known unpatched vulnerability. The static analysis reveals a substantial attack surface with 8 AJAX handlers, all of which lack authentication checks. This, coupled with a complete absence of nonce checks, makes these handlers highly susceptible to exploitation. Furthermore, the plugin exhibits concerning output escaping practices, with only 5% of outputs being properly escaped, increasing the risk of Cross-Site Scripting (XSS) vulnerabilities. The presence of the `unserialize` function, a known dangerous function, is also a red flag, especially when combined with potentially unsanitized data. Taint analysis, while not revealing critical or high severity flows, did show 10 flows with unsanitized paths, indicating potential avenues for data manipulation if exploited alongside other weaknesses.

The vulnerability history is particularly alarming. A medium severity CVE exists for this plugin, and critically, it is currently unpatched. The common vulnerability type being Cross-Site Request Forgery (CSRF) aligns with the observed lack of authentication and nonce checks. The last vulnerability was recorded in September 2025, suggesting a recent history of security issues. While the plugin doesn't have bundled libraries or custom REST API routes, the sheer number of unprotected entry points and the unpatched CVE heavily outweigh these minor strengths, making it a high-risk plugin.