WP-WebRTC2 Security & Risk Analysis

The wp-webrtc2 plugin version 1.7.4 presents a mixed security posture. While it demonstrates good practices by avoiding dangerous functions, file operations, and external HTTP requests, and has a clean vulnerability history with no recorded CVEs, there are significant concerns regarding its attack surface and input sanitization. The presence of four AJAX handlers without authentication checks is a major red flag, opening the door for unauthorized actions if these handlers are exploitable. This, coupled with a concerning 8 out of 11 analyzed taint flows having unsanitized paths, indicates a high potential for vulnerabilities, even if no critical or high severity issues were flagged in the static analysis. The plugin also shows a moderate concern with only 46% of its output being properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities.

While the absence of known vulnerabilities is positive, it does not guarantee the plugin's current safety, especially given the identified weaknesses. The moderate use of prepared statements for SQL queries and the limited number of nonce and capability checks suggest areas for improvement in securing the codebase. The overall risk assessment leans towards caution due to the significant number of unprotected entry points and the taint analysis results, despite the lack of historical CVEs.