Skip to content
Laskyr

SQL injection in WordPress plugins

SQL injection happens when a plugin puts user input straight into a database query. An attacker can then change the query to read data it was never meant to return, and sometimes to change it.

In WordPress that usually means reading the users table, including password hashes and email addresses. With a hash an attacker can try to crack the admin password offline. Records marked “no login needed” are the ones automated scanners go after first.

What to do: update to the fixed version right away. If you ran a vulnerable version on a site where anyone can reach the affected feature, change admin passwords, and check Users for accounts you do not recognise.

Worried a plugin bug was used on your site?

The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.

Newest SQL injection records

1,405 on record for the plugins we track; the newest 100 are below. Data as of 2026-11-04.

“Affected” is the version range the source gives. “Fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. Each CVE id links to the full record on the plugin’s page.

Other types

Browse vulnerabilities

Where this data comes from

← Check a plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit