jfgamsby

Blueternal BOLT Security Toolkit (BOLT) scans your WordPress site and hosting environment for security issues, surfaces plain-English findings in wp-admin, and gives you step-by-step fix instructions for every check.
BOLT is designed for the gap between generic WordPress security plugins and full server access: it helps site owners, agencies, and hosting teams see what is actually misconfigured on the current host, which issues matter most, and which ones BOLT can safely fix from WordPress plugin context.
Free features:
<ul>
<li>31-point security scan across Server Environment, WordPress Core, Authentication, Site Exposure, Security Headers, Updates, and Writable Directories</li>
<li>Checks PHP version, MySQL version, OPcache, dangerous PHP functions, directory listing, PHP override effectiveness, loopback request health, WP-Cron health, WP_DEBUG, wp-config.php permissions, DISALLOW_FILE_EDIT, database prefix, XML-RPC, REST API exposure, application passwords, user registration, default admin username, administrator account sprawl, debug log exposure, readme.html exposure, public backup or dump artifacts, HTTPS, HSTS, core/plugin/theme updates, uploads permissions, and executable files in uploads</li>
<li>Server/PHP profile detection for Apache, Apache with PHP-FPM/FastCGI, LiteSpeed/LSAPI, Nginx with PHP-FPM, IIS, and unknown/shared-host stacks</li>
<li>“How to fix” accordion with manual instructions for every check</li>
<li>Recommendations summary of all failing and warning items</li>
<li>Host-aware action states so supported fixes show as actionable and unsupported ones stay manual</li>
<li>Dedicated Hardening tab with supported one-click hardening actions and manual priorities</li>
<li>One-click auto-fixes for WP_DEBUG, File Editor, Directory Listing, HSTS, executable files in uploads, XML-RPC, and REST API restriction when the current host supports them</li>
<li>One-click removal for public readme.html exposure and public backup, dump, environment, installer, and diagnostic artifacts</li>
<li>Persistent fix history with grouped sessions and full undo for all BOLT-applied changes, including restoring original wp-config.php and .htaccess content</li>
<li>REST public-route allowlist manager for intentional unauthenticated REST endpoints</li>
<li>Application Password Governance inventory with stale, unused, and administrator-owned API credential review</li>
<li>Attack Path Analysis: identifies realistic compromise chains based on your current configuration and shows the fastest way to break them</li>
<li>Near-Miss Detection: highlights conditions that are close to forming an attack path before they become exploitable</li>
<li>AI Security Briefing panel is visible in the Overview tab; generation and AI Settings require BOLT Pro</li>
<li>Weekly scheduled scan reports by email</li>
<li>Optional BOLT-branded PDF attachment on scheduled scan emails using dompdf when available, with a built-in plain PDF fallback</li>
<li>Reports tab status panel showing whether the BOLT WP-Cron event is registered, when it will run next, the last delivery/PDF status, and a manual test-send button</li>
<li>Email only when new issues appear</li>
<li>Alerts tab shows the Slack and generic webhook controls; delivery and test alerts require BOLT Pro</li>
<li>Activity tab with the last 7 days of security timeline entries for logins, user changes, software changes, scans, reports, alerts, and auto-fixes</li>
<li>Baseline drift detection with one active baseline, save/update/clear baseline actions, regressions since the approved scan, and finding-level before/after value diffs</li>
<li>Vulnerability Intelligence rows can show pass/fail status and CVE IDs when advisory findings are present; full advisory detail requires BOLT Pro</li>
<li>Accepted Risk Register with owner, reason, expiration date, reopen controls, and action-queue suppression for documented unresolved findings</li>
</ul>
Available through the separate BOLT Pro add-on/service (<a href="https://blueternalsolutions.com/bolt-pro" rel="nofollow ugc">learn more at blueternalsolutions.com/bolt-pro</a>):
BOLT Pro adds more coverage and less manual work through hosted checks, automation, and reporting controls.
<ul>
<li>Domain/IP reputation scan through the BOLT platform endpoint, with normalized results from Spamhaus DBL, SURBL, URIBL, Spamhaus ZEN, SpamCop, and SORBS</li>
<li>On-demand reputation re-checks from the Reputation tab</li>
<li>WordPress core file integrity monitoring against official checksums</li>
<li>Unexpected-file detection inside wp-admin and wp-includes</li>
<li>PHP malware-pattern scanning across plugins, themes, mu-plugins, and uploads, with Malware Triage Center support for hash-based expected-file decisions</li>
<li>Vulnerability intelligence for WordPress core, plugins, and themes through a configurable BOLT advisory feed</li>
<li>Full vulnerability advisory detail, including affected version range, CVSS score, and patch link when supplied by the advisory feed</li>
<li>AI Security Briefings and AI Settings</li>
<li>Daily and monthly scheduled scan cadences</li>
<li>Multiple report recipients and custom report branding</li>
<li>Slack and generic webhook alerts, including critical-only and baseline-regression-only filters</li>
<li>Full Activity timeline</li>
<li>Named baseline snapshots</li>
</ul>
<h3>External Services</h3>
BOLT only sends data to an external service when the corresponding feature is configured or explicitly used by an administrator.
<h4>Blueternal Solutions</h4>
When a site has BOLT Pro active and an administrator generates the AI Security Briefing without saving their own OpenAI API key, BOLT sends a compact, redacted JSON payload of selected fail/warn scan findings to the Blueternal Solutions BOLT API for hosted analysis. Free installs show the AI panel but cannot generate briefings. The payload can include finding labels, statuses, severities, messages, recommendations, remediation guide URLs, limited environment notes, baseline drift summaries, a payload hash, plugin version, site/home URL, and a random install identifier used for service quota. It does not send raw files, database contents, passwords, secret keys, or arbitrary page content.
The hosted AI service uses Blueternal Solutions server-side credentials and may process the redacted payload through an AI provider to return the structured briefing. The separate BOLT Pro add-on/service may also contact Blueternal Solutions endpoints for license validation, reputation checks, vulnerability intelligence, and upgrade pages. Depending on the Pro feature used, requests may include the site URL, plugin version, license key, domain, IP address, and installed WordPress core/plugin/theme version metadata needed to return the requested service response.
Service endpoint: <code>https://blueternalsolutions.com</code> 
Terms: https://blueternalsolutions.com/bolt-terms-of-service/ 
Privacy policy: https://blueternalsolutions.com/bolt-privacy-policy/
<h4>OpenAI</h4>
If BOLT Pro is active and an administrator saves an OpenAI API key in BOLT settings or defines <code>BOLT_OPENAI_API_KEY</code>, the AI Security Briefing sends the compact, redacted JSON payload directly from the site to OpenAI instead of using the hosted BOLT service. The payload can include finding labels, statuses, severities, messages, recommendations, remediation guide URLs, limited environment notes, and baseline drift summaries. It does not send raw files, database contents, passwords, secret keys, or arbitrary page content.
Service endpoint: <code>https://api.openai.com</code> 
Terms: https://openai.com/policies/terms-of-use/ 
Privacy policy: https://openai.com/policies/privacy-policy/
<h4>Google Safe Browsing</h4>
If BOLT Pro is active and an administrator saves a Google Safe Browsing API key, the Browser Blocklist reputation check sends the site’s home URL and domain URL to the Google Safe Browsing Lookup API v4 when a reputation check runs. This is used only to determine whether the site is flagged for malware, phishing, unwanted software, or potentially harmful applications. The request also includes the saved API key, a BOLT client identifier, and the plugin version. BOLT does not send scan findings, files, database contents, passwords, license keys, or arbitrary page content to Google Safe Browsing.
Service endpoint: <code>https://safebrowsing.googleapis.com/v4/threatMatches:find</code> 
Terms: https://developers.google.com/terms 
Privacy policy: https://policies.google.com/privacy
<h4>Slack</h4>
If BOLT Pro is active and an administrator saves a Slack incoming webhook URL in BOLT Alerts, scheduled alerts or the manual test alert send alert text to the configured Slack webhook. The payload can include the site name, site URL, BOLT admin URL, scan score, score label, score delta, baseline score delta, issue count, issue labels, issue severities, issue statuses, issue messages, baseline drift summaries, capture time, and whether the alert is a test. It does not send raw files, database contents, passwords, secret keys, license keys, or arbitrary page content.
Service endpoint: the Slack incoming webhook URL configured by the administrator, usually <code>https://hooks.slack.com/services/...</code> 
Webhook documentation: https://api.slack.com/incoming-webhooks 
Terms: https://slack.com/terms-of-service/api 
Privacy policy: https://slack.com/privacy-policy
<h4>Generic Webhook</h4>
If BOLT Pro is active and an administrator saves a generic webhook URL in BOLT Alerts, scheduled alerts or the manual test alert send a JSON alert payload to the exact URL configured by that administrator. The payload can include the site name, site URL, BOLT admin URL, scan score, score label, score delta, critical-only and baseline-only alert flags, baseline score delta, issue count, issue labels, issue severities, issue statuses, issue messages, recommendations, baseline drift summaries, capture time, and whether the alert is a test. It does not send raw files, database contents, passwords, secret keys, license keys, or arbitrary page content.
Service endpoint: the generic webhook URL configured by the administrator. 
Terms and privacy policy: determined by the administrator-configured destination service.

Blueternal BOLT Security Toolkit

WordPress and hosting security scanner with plain-English findings, safe hardening actions, reports, and Pro AI summaries.

Guido Schad

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.
Current prototype features include:
<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>
Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.
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.

Lockora Security Audit

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

Blueternal BOLT Security Toolkit vs Lockora Security Audit