Meveto Security & Risk Analysis

The login-with-meveto-oauth-client plugin v3.0.2 exhibits a generally positive security posture based on the provided static analysis and vulnerability history. The absence of known CVEs and a history of no recorded vulnerabilities is a strong indicator of mature security practices and diligent maintenance. The code also demonstrates good habits with a high percentage of SQL queries using prepared statements and a reasonable proportion of properly escaped output. The limited attack surface, consisting only of shortcodes, with no AJAX handlers or REST API routes exposing functionality without authentication, further strengthens its security profile. The plugin also correctly implements capability checks on its sole file operation.

However, there are areas for concern. The most significant red flag is the taint analysis revealing 7 flows with unsanitized paths. While the severity is reported as critical and high (0), the sheer number of unsanitized paths, even if they don't currently lead to exploitable vulnerabilities, represents a latent risk. If any of these paths were to involve user-supplied input that is later used in file operations, database queries, or external requests, it could open the door to various attacks. Additionally, the lack of nonce checks on any entry points is a significant omission. While the current entry points are limited and potentially not exposed to direct user manipulation in a way that would immediately exploit this, it's a fundamental security control that should be present on all potential user-facing functions. The bundled Guzzle library also warrants attention for potential outdated versions, though specific details are not provided.