NERD WP Plugin Security & Risk Analysis

The "nerd-wp" v1.2.5 plugin exhibits a mixed security posture. On the positive side, it demonstrates good practices by exclusively using prepared statements for its SQL queries and avoiding file operations or external HTTP requests. The absence of recorded vulnerabilities and CVEs in its history suggests a generally stable and well-maintained codebase.

However, significant concerns arise from the static analysis. The plugin presents a single entry point via its REST API route, which completely lacks permission callbacks, making it accessible to unauthenticated users. Furthermore, only 28% of output is properly escaped, indicating a high potential for Cross-Site Scripting (XSS) vulnerabilities. While taint analysis shows no critical or high severity flows, the limited scope (0 flows analyzed) means this doesn't provide strong assurance of safety. The presence of the Guzzle library, if outdated, could also introduce risks, though the analysis doesn't specify its version.

In conclusion, "nerd-wp" v1.2.5 has strengths in its database query handling and lack of historical vulnerabilities. Nevertheless, the unprotected REST API route and widespread output unescaped are critical security weaknesses that require immediate attention to mitigate potential exploitation.