Inqyra Security & Risk Analysis

The "inqyra" v1.1.5 plugin exhibits a mixed security posture. On one hand, it demonstrates strong adherence to secure coding practices with 100% of SQL queries using prepared statements and all output properly escaped. The presence of numerous nonce and capability checks (42 and 43 respectively) also suggests an awareness of securing WordPress functionalities. Furthermore, the plugin's vulnerability history is clean, with no recorded CVEs, indicating a history of robust security.

However, a significant concern arises from the extensive attack surface exposed through AJAX handlers. All 24 identified AJAX handlers lack authentication checks, making them direct entry points for potential attackers. While no critical or high severity taint flows were explicitly detailed, the 5 flows with unsanitized paths within the analyzed 14 taint flows are a serious red flag. These unsanitized paths, combined with the unprotected AJAX endpoints, create a high probability of exploitation if an attacker can trigger these flows. The bundled libraries, Select2 and Freemius v1.0, also warrant attention for potential version-specific vulnerabilities, although no specific issues are detailed here.

In conclusion, "inqyra" v1.1.5 has strengths in its database interaction and output handling. Nevertheless, the lack of authentication on a large number of AJAX handlers and the presence of unsanitized paths in taint flows represent critical security weaknesses that significantly elevate the risk profile of this plugin. Immediate attention should be directed towards securing these AJAX endpoints.