Custom Field Builder – WordPress custom fields plugin Security & Risk Analysis

The "custom-field-builder" plugin version 1.2.4 exhibits a concerning security posture primarily due to a significant lack of input sanitization and authentication checks. The static analysis reveals one AJAX handler that does not implement any authentication checks, making it a direct entry point for potential attackers. Furthermore, all SQL queries are executed without prepared statements, indicating a high risk of SQL injection vulnerabilities. The taint analysis highlights two flows with unsanitized paths, both classified as high severity. This suggests that data entering the plugin is not being properly validated before being used in sensitive operations. While there is no recorded vulnerability history, this should not be interpreted as a sign of strong security, but rather a potential lack of past scrutiny or reporting. The limited attack surface is a minor positive, but it is overshadowed by the critical weaknesses identified in the code's handling of user input and database interactions. Without addressing the unauthenticated AJAX endpoint and the raw SQL queries, the plugin remains highly vulnerable.