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? – Ac
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.0 and PHP 7.4.
SourceWordPress plugins · Nov 4, 2026
01 / Source details
Aboutthistool.
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.
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.
02 / Source details
Gettingstarted.
01Upload the lockora-security-audit folder to /wp-content/plugins/ .
02Activate Lockora Security Audit from the Plugins screen.
03Go to Tools > Lockora Security Audit.
04Click Run Scan.
03 / Source details
Frequently asked questions.
Does Lockora Security Audit fix every issue automatically?
No. It provides reversible hardening toggles for selected low-risk settings. Other findings should be reviewed by an administrator, developer, or host.
Does Lockora Security Audit require AI?
No. The scanner works without AI on WordPress 6.0 and newer. AI client reports are optional and require WordPress 7.0 or newer with AI Client support plus a configured AI Connector.
Does Lockora Security Audit include a vulnerability database?
No. It can optionally use a configured Wordfence Intelligence API key for known vulnerability matching.
Does the wp-content scan validate every plugin and theme file?
No. Plugin, theme, must-use plugin, and language directories contain legitimate executable files and are excluded from this anomaly pass by default. Lockora checks their update and vulnerability posture separately. The anomaly scan focuses on uploads, the wp-content root, cache and upgrade locations, backups, and secret-like files.
Developers can tune the scan with the lockora_wp_content_allowed_files , lockora_wp_content_excluded_paths , lockora_wp_content_executable_extensions , lockora_wp_content_sensitive_extensions , lockora_wp_content_archive_extensions , lockora_wp_content_scan_max_files , and lockora_wp_content_max_reported_paths filters. Allowed and excluded paths are relative to the wp-content directory.
Does Lockora Security Audit send secrets to AI providers?
The plugin is designed to send sanitized scan findings only. It does not intentionally send passwords, salts, API keys, raw logs, user lists, or file contents.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati
