Lockora Security Audit

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.

Built and maintained by WP Server Guard, WordPress server security and hardening specialists.

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.

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.

org APIs:

* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data.

org when update data is refreshed.

org/about/terms/

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.

com/wordfence-intelligence-terms-and-conditions/

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.