YARPP – Yet Another Related Posts Plugin Security & Risk Analysis

The 'yet-another-related-posts-plugin' v5.30.11 exhibits a mixed security posture. While it demonstrates some good practices such as a moderate adoption of prepared statements and nonce checks, several areas raise concerns. The presence of one AJAX handler without authentication checks and two high-severity taint flows with unsanitized paths are significant weaknesses that could be exploited for unauthorized actions or data manipulation. Furthermore, the plugin's history of 8 CVEs, including a past critical vulnerability and frequent Cross-Site Scripting and SQL Injection issues, indicates a pattern of past security oversights, even though no critical CVEs are currently unpatched.

Despite the positive aspects like the absence of bundled libraries and a reasonable number of capability checks, the identified code signals like the use of `unserialize` and a low percentage of properly escaped outputs present further potential attack vectors. The considerable attack surface with one unprotected entry point and the vulnerability history suggest that while the plugin is actively maintained (indicated by the recent CVE), historical weaknesses may persist or recur. Users should be cautious and ensure they are on the latest version, but vigilance regarding its past vulnerability patterns is recommended.