Use InnoDB Security & Risk Analysis
wordpress.org/plugins/use-innodbIncreases performance by changing the storage engine of the options table from MyISAM to InnoDB.
Is Use InnoDB Safe to Use in 2026?
Generally Safe
Score 85/100Use InnoDB has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The 'use-innodb' v1.0.2 plugin presents a strong security posture based on the provided static analysis. The absence of any identified attack surface entry points (AJAX handlers, REST API routes, shortcodes, cron events) suggests a minimal footprint, which is generally a positive security trait. Furthermore, the code signals indicate good practices in output escaping, with 100% of outputs being properly escaped, and no dangerous functions, file operations, or external HTTP requests were detected. The lack of any reported vulnerabilities or CVEs historically is also a very reassuring indicator of the plugin's security track record.
Key Concerns
- Raw SQL queries without prepared statements
- No nonce checks implemented
- No capability checks implemented
Use InnoDB Security Vulnerabilities
Use InnoDB Code Analysis
SQL Query Safety
Use InnoDB Attack Surface
Maintenance & Trust
Use InnoDB Maintenance & Trust
Maintenance Signals
Community Trust
Use InnoDB Alternatives
No alternatives data available yet.
Use InnoDB Developer Profile
3 plugins · 2.0M total installs
How We Detect Use InnoDB
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.