ShMapper by Teplitsa Security & Risk Analysis

The "shmapper-by-teplitsa" plugin v1.5.1 presents a mixed security posture. While it demonstrates good practices in using prepared statements for a majority of its SQL queries and properly escaping most output, significant concerns arise from its attack surface. A substantial portion of its entry points, specifically 7 out of 11, lack authentication checks, making them vulnerable to unauthorized access and manipulation. Furthermore, the presence of 3 flows with unsanitized paths, although not classified as critical or high severity by the taint analysis, warrants attention as it suggests potential avenues for input injection vulnerabilities.

The plugin's vulnerability history is a notable weakness. With 2 known medium severity CVEs, both instances of Cross-site Scripting (XSS), it indicates a recurring pattern of input sanitization issues. The fact that the last vulnerability was recorded in early 2025, even though the current version might be older, suggests that past vulnerabilities may not have been adequately addressed or that the underlying code structure remains susceptible. The absence of unpatched vulnerabilities is a positive sign, but the history itself points to a need for more robust security development practices.

In conclusion, "shmapper-by-teplitsa" v1.5.1 has strengths in its SQL and output handling but suffers from critical weaknesses in its attack surface and a concerning history of XSS vulnerabilities. The unprotected AJAX handlers and unsanitized paths are immediate risks that require mitigation. The recurring XSS vulnerabilities, even if currently patched, highlight an ongoing risk that could resurface with future code changes. A proactive approach to hardening the input validation and authorization mechanisms is recommended.