DE

↑ ↓ select, Enter open, Esc close

Compare plugin files with the originals from wordpress.org

harmlessWP-CLIalle
Adjust the values, the command updates live
user@server
wp plugin verify-checksums --all --path=/var/www/vhosts/example.com/httpdocs

Compares the files of all installed plugins with the checksums on wordpress.org. Modified, missing and additional files are reported. Complements the core file check when you suspect a breach.

Note: Premium plugins that are not listed on wordpress.org cannot be verified this way and show up as errors.

Also searched as

  • scan wordpress plugin for malware
  • find tampered wordpress plugins
  • plugin files modified

Related one-liners

All in WP-CLI

Check WordPress core files for tampering

$wp core verify-checksums --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Deactivate a single plugin despite a PHP fatal error

$wp plugin deactivate woocommerce --skip-plugins --skip-themes --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Deactivate all plugins and save the active list

$wp plugin list --status=active --field=name --path=/var/www/vhosts/example.com/httpdocs > /var/www/vhosts/example.com/active-plugins.txt && wp plugin deactivate --all --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

List all WordPress administrators

$wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

List installed plugins with status and updates

$wp plugin list --fields=name,status,version,update_version --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Regenerate WordPress security keys (salts)

$wp config shuffle-salts --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.