Ben Treder

<p>Treder Security Snapshot gives WordPress site owners a simple local security health report.</p>
<p>It is not a firewall, malware removal tool, or all-in-one security suite. It focuses on clear visibility, practical recommendations, and easy reporting.</p>
<p>The plugin checks common WordPress security basics and gives you a security score from 0 to 100.</p>
<h4>Included Features</h4>
<ul>
<li>Security score from 0 to 100</li>
<li>Dashboard tab</li>
<li>Detailed audit tab</li>
<li>Scan history tab</li>
<li>WordPress dashboard widget</li>
<li>Beginner-friendly explanations</li>
<li>Suggested fixes</li>
<li>Local scan history</li>
<li>Local HTML report download</li>
<li>Email latest report to a chosen address</li>
</ul>
<h4>Security Checks</h4>
<ul>
<li>WordPress core update status</li>
<li>Plugin update status</li>
<li>Theme update status</li>
<li>Default admin usernames</li>
<li>User enumeration risk</li>
<li>XML-RPC status</li>
<li>File editing status</li>
<li>Debug mode status</li>
<li>Directory browsing indicators</li>
<li>HTTPS and SSL status</li>
<li>Database prefix check</li>
<li>WordPress version visibility</li>
<li>Public registration status</li>
<li>Inactive plugins</li>
</ul>
<h4>Separate Pro Companion</h4>
<p>A separate Pro companion plugin is available from the author’s website for users who want additional tools such as advanced checks, scheduled reports, file integrity monitoring, white-label reporting, and AI-assisted fix plans.</p>
<p>The WordPress.org plugin includes all functionality described in this readme.</p>


Treder Security Snapshot

A lightweight WordPress security health report with a simple score, clear findings, local reports, and beginner-friendly suggested fixes.

Guido Schad

<p>Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.</p>
<p>Current prototype features include:</p>
<ul>
<li>Manual security scans.</li>
<li>Weighted security score out of 100.</li>
<li>WordPress core file integrity checks using official checksums.</li>
<li>WordPress authentication key and salt checks, with an explicit action to generate missing salts.</li>
<li>Must-use plugin directory presence checks.</li>
<li>PHP version status using WordPress.org Serve Happy data.</li>
<li>HTTPS and HTTP security header checks.</li>
<li>WordPress core, plugin, and theme update posture checks.</li>
<li>Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory.</li>
<li>Optional known vulnerability matching with a configured Wordfence Intelligence API key.</li>
<li>Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured.</li>
<li>Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers.</li>
</ul>
<h3>External Services</h3>
<p>Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.</p>
<p>WordPress.org APIs:<br />
* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data.<br />
* 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.<br />
* WordPress.org terms: https://wordpress.org/about/terms/<br />
* WordPress.org privacy policy: https://wordpress.org/about/privacy/</p>
<p>Wordfence Intelligence:<br />
* Optional.<br />
* Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching.<br />
* Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions.<br />
* 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.<br />
* Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/<br />
* Wordfence privacy policy: https://www.wordfence.com/privacy-policy/</p>
<p>WordPress AI Client / Connectors:<br />
* Optional.<br />
* Used only when the administrator clicks Generate Client Report.<br />
* 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.<br />
* The configured AI provider is controlled by the site owner’s WordPress Connector settings.<br />
* 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.</p>


Lockora Security Audit

Lockora Security Audit checks WordPress security posture, hardening, core integrity, vulnerabilities, and optional AI reports.

Treder Security Snapshot vs Lockora Security Audit