Omnipress Security & Risk Analysis

The omnipress plugin v1.6.7 presents a mixed security posture. On the positive side, the plugin demonstrates good practices in several areas, including 100% of SQL queries using prepared statements, a high percentage of properly escaped output, and a substantial number of nonce and capability checks, indicating an awareness of common WordPress security vulnerabilities. However, significant concerns are raised by the presence of unprotected entry points and historical vulnerability patterns.

The static analysis reveals one unprotected REST API route, which is a critical entry point that could be exploited without proper authorization checks. While taint analysis shows no critical or high-severity unsanitized flows, the presence of 5 flows with unsanitized paths, even if categorized as lower severity, warrants attention as potential avenues for exploitation. The plugin also performs a considerable number of file operations and external HTTP requests, which, if not handled securely, could introduce risks.

The vulnerability history is a major red flag. With 6 known CVEs, 2 of which are currently unpatched, and a history including high and medium severity vulnerabilities like PHP Remote File Inclusion, Cross-site Scripting, and Authorization Bypass, the plugin has a proven track record of exploitable weaknesses. The recurrence of specific vulnerability types suggests systemic issues in code sanitization and access control. While the last vulnerability was in 2026 (a future date, likely a typo in the provided data, but assuming it reflects past activity), the existence of unpatched vulnerabilities is a severe risk. The plugin's strengths in prepared statements and output escaping are overshadowed by the historical prevalence of vulnerabilities and the identified unprotected entry point, suggesting a high overall risk for sites using this version.