Propel Security & Risk Analysis

The "propel" plugin v2.0.4 exhibits a mixed security posture. While it has no recorded vulnerability history and uses prepared statements for the majority of its SQL queries, several concerning patterns emerge from the static analysis. The plugin presents an attack surface with 3 entry points, one of which is an AJAX handler that lacks authentication checks. This is a significant concern as it could allow unauthenticated users to trigger potentially sensitive functionality.

Taint analysis reveals two high-severity flows with unsanitized paths, indicating potential risks of injection or unintended data manipulation if user-supplied data is not properly validated and sanitized before being used. Furthermore, a substantial 91% of output is not properly escaped, posing a risk of Cross-Site Scripting (XSS) vulnerabilities where user-controlled data displayed on the frontend could contain malicious scripts. The bundled DataTables library at v1.7.6 is also outdated, which could be a vector for exploits if vulnerabilities exist in that specific version.

Despite the absence of known CVEs, the identified code-level weaknesses, particularly the unauthenticated AJAX handler, high-severity unsanitized flows, and widespread output unescaping, create significant potential for exploitation. The plugin's strengths lie in its lack of direct file operations or external HTTP requests and its generally good use of prepared statements for SQL. However, the identified issues necessitate immediate attention to mitigate the risks.