kontur Admin Style Security & Risk Analysis

The plugin "kontur-admin-style" v1.0.5 exhibits a generally good security posture based on the static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points significantly limits the attack surface. Furthermore, the code signals show no dangerous functions, no raw SQL queries, and no file operations or external HTTP requests, which are all positive indicators of secure coding practices. The 100% use of prepared statements for SQL queries is particularly commendable.

However, there are areas for improvement. The "Capability checks" and "Nonce checks" are reported as zero, which, in conjunction with the 0% of AJAX handlers and REST API routes having permission callbacks, suggests a potential for authorization bypass vulnerabilities if any of these entry points were to be introduced or exist in a less obvious manner. The 79% of output escaping is good, but the remaining 21% of unescaped outputs, although not flagged as critical in taint analysis, could still pose a Cross-Site Scripting (XSS) risk, especially given the plugin's history of XSS vulnerabilities.

The vulnerability history reveals one past CVE, specifically related to Improper Neutralization of Input During Web Page Generation (XSS). While this CVE is currently unpatched, its presence and type, coupled with the incomplete output escaping, indicates a recurring risk pattern. The fact that the "Last vulnerability" is in the future (2025-09-26) is likely a data anomaly and should be disregarded. In conclusion, while the plugin demonstrates strong defensive coding in several areas, the lack of capability and nonce checks, combined with a history and potential for XSS, warrants careful monitoring and potential remediation.