Popularis Extra Security & Risk Analysis

The 'popularis-extra' plugin v1.2.10 exhibits a mixed security posture. On the positive side, static analysis reveals a robust implementation of security controls, with all identified entry points (AJAX handlers, REST API routes, shortcodes, and cron events) appearing to have authentication or permission checks. SQL queries are consistently prepared, and a significant majority of output is properly escaped, indicating good development practices in these areas. Nonce and capability checks are also prevalent.

However, the presence of the `unserialize` function is a significant concern, as it can lead to remote code execution vulnerabilities if not handled with extreme care and strict input validation. While no critical or high severity taint flows were identified, the three flows with unsanitized paths, even if of lower severity in this analysis, warrant attention and further investigation to ensure they do not expose the application. The plugin's vulnerability history is also a red flag, with three known medium severity CVEs and, most critically, one currently unpatched vulnerability. The historical pattern of CSRF, authorization bypass, and XSS indicates a recurring tendency for vulnerabilities to emerge in these attack vectors.

In conclusion, while 'popularis-extra' demonstrates strengths in input sanitization and authentication mechanisms for its entry points, the `unserialize` function, unsanitized paths in taint flows, and a history of unpatched vulnerabilities present substantial risks. The single unpatched CVE significantly lowers the plugin's overall security rating. Users should exercise caution and prioritize updating to a version that addresses all known vulnerabilities.