SQL Executioner · Security record
Is SQL Executioner safe?
No known vulnerabilities are on record for SQL Executioner.
Checked 4 days ago against the WPVulnerability database, for version 1.4.
How it’s looked after
- Last release
- Sep 28, 2016 (10 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 4.6.30 (current: 7.1)
- Active installs
- 2K+
Known vulnerabilities
None on record for SQL Executioner.
Questions about SQL Executioner’s security
Is SQL Executioner safe to use?
No known vulnerabilities are on record for SQL Executioner. That isn’t a guarantee, so keep it updated like any plugin.
Does SQL Executioner have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for SQL Executioner.
Is SQL Executioner still maintained?
Its last release was 10 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is SQL Executioner compatible with the latest WordPress?
SQL Executioner’s readme says it’s tested up to WordPress 4.6.30, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.