WP Tesseract Security & Risk Analysis

The wp-tesseract v1.0.2 plugin presents a mixed security posture. On the positive side, its static analysis shows no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in zero identified entry points and no unprotected ones. Furthermore, all SQL queries appear to be properly prepared, mitigating a common class of vulnerabilities. The absence of external HTTP requests also reduces the risk of server-side request forgery or infection from compromised external resources.

However, significant concerns arise from several code signals. The presence of the 'exec' function is a critical red flag, as it can be exploited for remote code execution if improperly handled. Compounding this, 100% of output escaping is missing, meaning any data processed and displayed by the plugin is vulnerable to Cross-Site Scripting (XSS) attacks. The plugin also performs file operations without clear indication of their security context or sanitization.

The vulnerability history, particularly the existence of one unpatched medium severity CVE related to XSS, reinforces the output escaping concerns. The fact that this vulnerability is recent and unpatched is a major risk. While the attack surface seems limited in terms of direct entry points, the combination of a dangerous function ('exec'), lack of output escaping, and an existing XSS vulnerability, which is a common vulnerability type for this plugin, indicates a substantial risk of compromise.