WP-Polls Security & Risk Analysis

The wp-polls plugin v2.77.3 presents a mixed security posture. While it has a relatively small attack surface and incorporates some good security practices like nonce and capability checks, significant concerns emerge from its vulnerability history and static analysis findings. The plugin has a substantial history of known CVEs, including critical and high-severity issues, indicating a pattern of recurring security weaknesses. This history, coupled with the presence of two high-severity taint flows with unsanitized paths, strongly suggests potential for SQL Injection or other injection vulnerabilities if these flows are not properly handled in downstream processing. The 42% of SQL queries not using prepared statements is also a notable area of risk. While the plugin appears to have addressed past critical and high vulnerabilities, the historical trend is concerning and suggests a need for continued vigilance and diligent patching.

Despite the presence of bundled libraries like TinyMCE, which can sometimes introduce vulnerabilities if outdated, and a moderate percentage of improperly escaped outputs, the most pressing issues stem from the taint analysis and the historical CVE data. The plugin's zero unprotected entry points is a positive sign, but the identified taint flows and past vulnerabilities paint a picture of a plugin that, while functional, has a history of security oversights that could be exploited. A more robust approach to input sanitization and prepared statements across all database interactions would significantly improve its security standing. The fact that all previously disclosed CVEs are currently unpatched is a positive indicator for this specific version, but the overall trend warrants caution.