Nexter Extension – Security, Performance, Code Snippets & Site Toolkit Security & Risk Analysis

The 'nexter-extension' plugin version 4.6.0 exhibits a mixed security posture. While it demonstrates good practices such as a high percentage of SQL queries using prepared statements and a substantial number of nonce and capability checks, there are significant areas of concern. The presence of unprotected AJAX handlers is a primary risk, potentially allowing unauthorized actions if these handlers are not properly secured within the plugin's logic. The static analysis also flagged dangerous functions like 'shell_exec' and 'unserialize', which, when combined with unsanitized input flows, could lead to serious vulnerabilities like code injection or deserialization flaws.

The vulnerability history, with four known CVEs including high and medium severity issues such as Deserialization of Untrusted Data, Cross-site Scripting, and Code Injection, indicates a pattern of past security weaknesses. The fact that all previously identified CVEs are now patched is positive, but the types of vulnerabilities suggest a recurring need for careful input validation and secure coding practices. The last vulnerability recorded, while in the future (2026), might be an artifact of data generation but highlights the importance of ongoing vigilance and timely patching.

In conclusion, while the plugin has strengths in its use of prepared statements and checks, the unprotected entry points, dangerous functions, and historical vulnerability types present a notable risk. The taint analysis showing flows with unsanitized paths further exacerbates these concerns. Continued development attention is needed to address the unprotected AJAX handlers and ensure all input is rigorously validated and sanitized before being processed by dangerous functions.