Map Navigator Security & Risk Analysis

The mapnavigator plugin version 1.1.0 exhibits a concerning security posture due to significant vulnerabilities identified in the static analysis. A major red flag is the presence of three AJAX handlers that lack authentication checks, creating a substantial attack surface. Furthermore, the taint analysis revealed three high-severity flows with unsanitized paths, indicating potential for attackers to inject malicious data. The plugin also heavily relies on dangerous functions like `unserialize` and `create_function`, which are often associated with security risks if not handled with extreme care. The output escaping is also alarmingly poor, with only 5% of outputs properly escaped, increasing the risk of cross-site scripting (XSS) vulnerabilities.

While the plugin has no recorded CVEs, this historical absence of public vulnerabilities should not be interpreted as a sign of robust security, especially given the critical findings in the static analysis. The low percentage of prepared SQL statements (81%) also presents a risk of SQL injection, although less severe than the other identified issues. The lack of nonce checks on AJAX endpoints is another critical oversight. The plugin's strength lies in its clean vulnerability history and absence of bundled libraries, but these are overshadowed by the severe security flaws present in its current version.