WP Post Corrector Security & Risk Analysis

The "wp-post-corrector" plugin v1.0.2 exhibits a concerning security posture, largely due to significant weaknesses identified in its code and a history of known vulnerabilities. While the static analysis reports a small attack surface with no apparent direct entry points like AJAX, REST API, or shortcodes, this masks deeper issues. The critical concern lies in the lack of proper output escaping, with 0% of 53 identified outputs being properly sanitized. This, combined with a high proportion of SQL queries (18 total) not using prepared statements (only 11%), creates a significant risk for SQL injection and Cross-Site Scripting (XSS) vulnerabilities.

The taint analysis, though limited in scope (4 flows analyzed), reveals that all flows have unsanitized paths, indicating potential avenues for malicious input to reach sensitive functions. The absence of nonce checks and capability checks for any functionality is a major security oversight, leaving any potential future entry points vulnerable to unauthorized access and manipulation. Furthermore, the plugin has a history of 2 known medium-severity vulnerabilities, specifically SQL injection and XSS, with both remaining unpatched as of the last vulnerability disclosure in June 2025. This pattern of past and persistent vulnerabilities, coupled with the identified code weaknesses, suggests a lack of robust security practices in the plugin's development and maintenance.

In conclusion, while the plugin's current apparent attack surface is small, the underlying code quality and vulnerability history present significant risks. The lack of output escaping, the prevalence of raw SQL queries, and the history of unpatched vulnerabilities are serious red flags. The absence of basic security checks like nonces and capability checks exacerbates these risks. Users should exercise extreme caution and consider disabling or thoroughly reviewing this plugin until these critical issues are addressed.