Yada Wiki Security & Risk Analysis

The yada-wiki plugin v3.6 exhibits a mixed security posture. On the positive side, it demonstrates good practices by consistently using prepared statements for all its SQL queries, indicating a strong defense against SQL injection. Furthermore, the absence of file operations and external HTTP requests limits potential attack vectors. However, the plugin has a significant concern regarding output escaping, with only 47% of outputs being properly escaped. This suggests a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, which is corroborated by its vulnerability history.

The plugin's attack surface includes a single AJAX handler that lacks authentication checks, presenting an immediate entry point for unauthenticated attackers. While there are no critical or high severity taint flows, the general lack of proper output escaping is a pressing issue. The plugin's history reveals two medium-severity Cross-Site Scripting (XSS) vulnerabilities, with the most recent one being in late 2025, suggesting a recurring pattern of input validation and output sanitization weaknesses. Although there are no currently unpatched vulnerabilities, the past issues highlight a need for more rigorous security testing and development practices.

In conclusion, the yada-wiki plugin v3.6 has some solid security foundations, particularly in its SQL handling. Nevertheless, the prevalence of improperly escaped output and an unprotected AJAX endpoint are critical weaknesses that require immediate attention. The historical XSS vulnerabilities underscore a persistent problem that needs to be addressed to improve the plugin's overall security and prevent future compromises.