MCL Security Scanner

Description

MCL Security Scanner checks your WordPress site for the problems hacked sites usually have, explains each finding in plain language, and lets you fix many of them with one click. Every fix is logged and most can be undone.

Scans are read-only. Nothing on your site changes until you tick “I have a recent backup” and click a Fix button.

What it scans

  • Database: spam posts and pages, hidden spam links, infected revisions, injected scripts in widgets and settings, spam tags and categories, spam comments, suspicious media, hidden and recently created administrators, suspicious scheduled tasks.
  • Plugin and theme code: backdoors, web shells, obfuscated code, code that creates admin users, SQL-injection risks, hidden links, search-engine cloaking and pirated-license code.
  • One plugin or theme: scan a single plugin or theme, plus a comparison with the official WordPress.org copy for free plugins.
  • Hidden files: files and folders starting with a dot, exposed .env and .git folders, dangerous .htaccess / .user.ini rules.
  • Uploads folder: PHP files, PHP hidden inside images, scripts in SVG/HTML files, database dumps and spam file names.
  • WordPress core: compares core files with the official WordPress.org checksums.
  • Plugins vs originals: compares each free plugin with its official WordPress.org package.
  • Configuration: wp-config.php checks (secrets are never shown), debug logs, pending updates, unused plugins and themes.

Safe fixes

  • Move suspicious files to a protected quarantine folder (files are renamed so they can never run).
  • Replace an infected WordPress.org plugin or theme with a fresh official copy of the same version (a backup is kept).
  • Remove hidden spam links from posts, fields and settings.
  • Demote suspicious administrators, remove hidden admin powers, delete spam terms and comments.
  • Undo most fixes from the “Fix log & Undo” screen.

Large sites are scanned in short chunks with a “Continue” button, so the scanner never slows your site down for visitors.

Privacy

The plugin does not track you, show ads or collect any data for its author. Scan results, the fix log and quarantined files stay on your own server.

The only outgoing requests go to WordPress.org, and only when an administrator runs a scan or clicks a Fix button. They send your WordPress version and locale, and the slug and version of installed plugins and themes, so the official files can be compared. No personal data, user data or site content is sent. Details are listed under “External services” below.

External services

To check whether files have been changed, the plugin compares them with the official copies published by WordPress.org. It only contacts WordPress.org, and only when an administrator runs a scan or clicks a Fix button.

  • WordPress.org core checksums API (api.wordpress.org/core/checksums/): used by the “WordPress core” scan. Sends your WordPress version and locale.
  • WordPress.org plugin checksums (downloads.wordpress.org/plugin-checksums/): used by the plugin scans. Sends the slug and version of each installed plugin being checked.
  • WordPress.org plugins and themes information API (api.wordpress.org/plugins/info/ and api.wordpress.org/themes/info/): used to confirm a plugin or theme is the same product as on WordPress.org and to get the official download link before a “Replace with official copy” fix. Sends the plugin or theme slug.
  • WordPress.org downloads (downloads.wordpress.org): when you choose “Replace with official copy”, the official package is downloaded and installed with WordPress’s own installer, exactly like a normal update.

No personal data, user data or site content is sent. These services are provided by WordPress.org: Privacy Policy.

Source code

All source code is included in the plugin in readable, unminified form: mcl-security-scanner.php, assets/admin.js and assets/admin.css. There is no build step and no third-party library.

Installation

  1. Install the plugin from Plugins > Add New, or upload the mcl-security-scanner folder to /wp-content/plugins/.
  2. Activate it.
  3. Open MCL Security in the admin menu and run the scans, starting with Database and Plugin & theme code.
  4. Before clicking any Fix button, make a full backup of your files and database.

FAQ

Will scanning change anything on my site?

No. Scans only read files and the database. Changes happen only when you click Fix and confirm you have a backup.

Can I undo a fix?

Most fixes can be undone from MCL Security > Fix log & Undo. Fixes that delete data permanently (for example emptying spam comments) are clearly labelled.

Where are quarantined files kept?

In a randomly named folder inside uploads/mcl-security-scanner/, protected from web access. Files are renamed to .quarantined so they cannot run. You can permanently delete them from the Fix log screen.

Who can use the scanner?

Only administrators (on multisite, only Super Admins).

Does it work on large sites?

Yes. File scans run in short chunks; click “Continue scan” until it finishes.

It flagged something I know is safe.

Some patterns (for example code that creates users) are normal in membership or form plugins. Each finding explains why it was flagged, so you can decide. Nothing is changed automatically.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“MCL Security Scanner” is open source software. The following people have contributed to this plugin.

Contributors

Translate “MCL Security Scanner” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

3.7.3

  • Multisite: Undo re-activates a plugin network-wide when it was network-active before the fix
  • Multisite: hidden network-active plugins are detected too

3.7.2

  • “Replace with official copy” now requires stronger proof that a plugin or theme is the wordpress.org one (file checksums for plugins; exact name, author and published version for themes)
  • Supports themes in additional registered theme directories
  • Admin JavaScript and CSS are formatted for readability

3.7.1

  • Hidden files scan and quarantine now support content, plugin, theme and uploads folders located outside the WordPress root
  • Quarantine moved to uploads/mcl-security-scanner/ (older quarantined files can still be restored)
  • Unique prefix for all functions, options, hooks and admin pages
  • PHP time limit is only extended while a scan is running

3.7.0

  • Prepared for the WordPress.org plugin directory
  • Admin CSS and JavaScript are now loaded as proper enqueued files
  • All database scan queries now use prepared statements
  • Quarantine folder moved to the uploads directory; files from older versions can still be restored and purged
  • File moves and deletes now use the WordPress filesystem API
  • Safer handling of unreadable files during scans
  • Added readme with documentation of the WordPress.org services used

3.6.1

  • Previous private release