Lockora Security Audit vs SiteCare – Vulnerability Scanner

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area. Works well with Who Changed It? Lockora finds security weaknesses. Who Changed It? – Activity Log shows what changed, who changed it, and when, with severity classification, field-level diffs, and alerts. Use both together to connect a security finding to the activity that caused it. Current prototype features include: Manual security scans. Weighted security score out of 100. Bounded scan history with current-versus-previous finding comparisons. WordPress core file integrity checks using official checksums, with CSV and TXT exports. Bounded wp-content anomaly scanning for executable uploads, unexpected PHP files outside standard code directories, runtime executables, and exposed backup or secret-like files, with CSV/TXT exports and clipboard copying. WordPress authentication key and salt checks, with explicit actions to generate missing salts or rotate the keys stored in wp-config.php. Must-use plugin directory presence checks. PHP version status using WordPress.org Serve Happy data. HTTPS and HTTP security header checks. WordPress core, plugin, and theme update posture checks. Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory. Public exposure checks: debug.log and readme.html reachability, uploads directory listing, PHP execution inside uploads, and author archive user enumeration. SSL certificate expiry check, database table prefix check, automatic update posture check, and detection of login protection / two-factor plugins. Site Health integration: scan summary plus key configuration checks appear under Tools > Site Health > Status. WP-CLI support: wp lockora scan and wp lockora report, with --format=json and a --strict flag for CI pipelines. Optional known vulnerability matching with a configured Wordfence Intelligence API key. Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured. Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers. A lockora_scan_completed action for integrations that need scan scores and finding counts. External Services Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report. During a scan the plugin also sends HTTP requests to the site’s own public URL (loopback requests) to inspect response headers, debug.log and readme.html reachability, uploads directory behavior, and author archive redirects, and it opens a TLS connection to the site’s own hostname to read the SSL certificate expiry date. These requests stay within the site being scanned and send no data to third parties. WordPress.org APIs: * Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data. * Data sent: the site’s WordPress version and locale for core checksums and PHP compatibility; WordPress itself may send installed plugin and theme slugs/versions to WordPress.org when update data is refreshed. * WordPress.org terms: https://wordpress.org/about/terms/ * WordPress.org privacy policy: https://wordpress.org/about/privacy/ Wordfence Intelligence: * Optional. * Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching. * Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions. * Data sent: the configured Wordfence Intelligence API key is sent in an Authorization header when requesting the vulnerability feed. Installed software details are not sent by this plugin to the Wordfence Intelligence endpoint; matching is performed locally after the feed is retrieved. * Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/ * Wordfence privacy policy: https://www.wordfence.com/privacy-policy/ WordPress AI Client / Connectors: * Optional. * Used only when the administrator clicks Generate Client Report. * Data sent: sanitized scan findings, score, counts, and recommendations needed to generate a client-facing report. The plugin is designed not to send passwords, salts, API keys, raw logs, full user lists, or file contents. * The configured AI provider is controlled by the site owner’s WordPress Connector settings. * Terms and privacy policy: these depend on the AI provider configured by the site owner in WordPress. Site owners should review the selected provider’s terms and privacy policy before enabling AI reports.

Most compromised WordPress sites aren’t hit by some clever, brand-new exploit – they’re breached through a known vulnerability in an outdated plugin or theme that nobody noticed in time. The fix is almost always as simple as running an update. The hard part is knowing there’s a problem at all. SiteCare Vulnerability Scanner watches that blind spot for you. It checks your installed plugins, themes, and WordPress core against a continuously updated database of publicly known vulnerabilities, then tells you in plain language – right in your dashboard – what is affected and what to do about it. Automatic daily monitoring in the background – plus an instant re-scan whenever you install, update or activate a plugin or theme. Email alerts the moment a new vulnerability appears, so you find out without having to be logged in. Clear severity ratings (CVSS) and CVE references, with the most urgent components listed first. One-click updates right from the results whenever a fix is available. Security score A-F (0-100) that grades your whole site at a glance, with a trend against your previous scan. Abandoned & removed plugin detection – warns you when an installed plugin has been closed on WordPress.org or has had no update for years. Slack / Discord alerts via webhook, and a WP-CLI command (wp vulnerability scan) with a CI-friendly exit code. Shown where you already look – a dashboard widget and a WordPress Site Health check. Your site’s data never leaves your server. The plugin only reads public vulnerability information through the WP Vulnerability API – no account, no external tracking, and no noticeable impact on performance. Key Features Accurate version-range detection against a continuously updated vulnerability database Automatic background scans (daily, configurable) with instant re-checks after site changes Email alerts for newly discovered vulnerabilities – only new ones, never repeated Severity ratings (CVSS), CVE references and “fixed in” versions One-click updates for affected plugins, themes and WordPress core Dashboard widget and WordPress Site Health integration Security score (A-F / 0-100) with a trend against the previous scan Detection of abandoned and removed (closed) plugins via the WordPress.org API Slack and Discord notifications through a webhook URL WP-CLI command (wp vulnerability scan / status) with a CI-friendly exit code Ships fully translated into five world languages – German, Spanish, French, Portuguese and Russian – plus Czech. Read-only: only component slugs and versions are sent; no data leaves your site Support development via Buy Me a Coffee License This plugin is distributed under the GNU General Public License v2.0 or later. See the license.txt file for details.