WP Admin Audit Security & Risk Analysis

The wp-admin-audit plugin, v1.2.16, exhibits a mixed security posture. On the positive side, the plugin demonstrates good practices regarding SQL queries, with almost all using prepared statements, and a high percentage of output being properly escaped. The plugin also incorporates a significant number of nonce checks and a reasonable number of capability checks, which are crucial for WordPress security. Furthermore, its vulnerability history is clean, with no known CVEs, suggesting a commitment to secure development or at least good luck to date.

However, a significant concern arises from the plugin's attack surface. With 29 AJAX handlers identified, a staggering 28 of them lack authentication checks. This creates a large potential entry point for malicious actors to interact with the plugin's functionalities without proper authorization. While taint analysis did not reveal critical or high severity issues, the presence of one flow with unsanitized paths, even if of lower severity, is a red flag. The use of bundled libraries like Select2 also presents a potential risk if not kept up-to-date, though no specific version issues were reported.

In conclusion, while the plugin shows strengths in database interaction and output handling, and benefits from a clean vulnerability history, the substantial number of unprotected AJAX endpoints poses a considerable risk. This, combined with the single identified unsanitized path flow, warrants attention. The plugin's security would be significantly improved by implementing proper authentication and capability checks on all its AJAX handlers.