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.

Esteban

Aipatch Security Scanner is a modular security audit engine built for site owners, developers, and AI-powered agents who need deep visibility into WordPress security posture — without the bloat of all-in-one security suites.
<h4>Why Aipatch Security Scanner?</h4>
Most WordPress security plugins are either too simple to be useful or too heavy to be practical. Aipatch takes a different approach:
<ul>
<li>Audit-first architecture. Every check is a standalone, testable module that returns structured findings with severity, confidence, evidence, and fingerprints.</li>
<li>Built for automation. 23 MCP abilities expose the full audit, scanning, and remediation surface to external AI agents — making Aipatch the first WordPress security plugin designed for agentic workflows.</li>
<li>Zero external dependencies. Everything runs locally. No accounts, no cloud services, no API keys required.</li>
<li>Reversible by design. Every automated remediation stores rollback data so you can undo any change with one click.</li>
</ul>
<h4>Core Capabilities</h4>
36-Point Security Audit
Aipatch runs 36 automated checks across 8 categories — core, plugins, themes, users, configuration, server, access control, and malware surface:
<ul>
<li>Outdated WordPress core, plugins, and themes</li>
<li>Default admin username, excessive admin accounts, inactive admin users, user ID 1 exposure</li>
<li>XML-RPC, file editor, debug mode, debug log, REST API exposure, directory listing</li>
<li>PHP version, HTTPS, file permissions, security headers (X-Frame-Options, CSP, etc.)</li>
<li>Database prefix, sensitive files, PHP execution in uploads, auto-update configuration</li>
<li>Salt key strength, cron health, cookie security flags, CORS, application passwords</li>
<li>Exposed backup files, phpinfo files, uploads directory indexing, default login URL</li>
<li>Database credential security, file installation permissions</li>
</ul>
Every finding includes a severity (critical / high / medium / low / info), confidence score, human-readable explanation, and actionable recommendation.
Weighted Security Score (0–100)
A logarithmic scoring engine computes an overall security score and per-area breakdown across six risk dimensions: software, access control, configuration, infrastructure, malware surface, and vulnerability exposure. Severity weights and confidence multipliers ensure the score reflects actual risk, not just issue count.
Multi-Layer Malware File Scanner
A three-layer file scanner (content 55%, context 25%, integrity 20%) with 27 detection signatures, Shannon entropy analysis, and malware family classification detects:
<ul>
<li>Code execution patterns: eval(), assert(), create_function(), preg_replace /e</li>
<li>System command functions: shell_exec, exec, passthru, backtick operators</li>
<li>Obfuscation techniques: base64 encoding, hex encoding, str_rot13, gzinflate chains, chr() concatenation, variable variables, suspiciously long lines</li>
<li>Network/exfiltration: cURL execution, fsockopen, remote file_get_contents</li>
<li>Known backdoor signatures: c99, r57, WSO, b374k, weevely, FilesMan</li>
<li>WordPress-specific threats: unauthorized admin creation, critical option injection, security function removal</li>
</ul>
Scanning runs in batches via an async job system with configurable batch sizes — safe for shared hosting.
Files are classified into 11 malware families (web shell, obfuscated loader, dropper, persistence backdoor, cloaked PHP, code injector, and more) with confidence scores and remediation hints.
WordPress Core Integrity Verification
Verifies every core file against official checksums from api.wordpress.org. Detects modified core files (checksum mismatch), missing core files, and unexpected files planted in wp-admin/ or wp-includes/. Core tampering findings are automatically escalated to critical severity with zero false-positive likelihood.
File Integrity Baseline
Build a known-good hash baseline of all PHP files in your installation. Diff against it at any time to detect modified, deleted, or newly added files. Origin detection distinguishes core, plugin, theme, and upload files.
Vulnerability Intelligence
A local knowledge base of known plugin, theme, and core vulnerabilities with a database-backed caching layer for fast lookups. Provider architecture allows extending with external feeds.
One-Click Remediation with Rollback
Apply fixes directly from findings — change WordPress options, delete suspicious files, rename files, patch file contents, or add .htaccess rules. Every automated action stores a full rollback payload so you can reverse any change. Manual remediations can be logged for audit trails.
Six supported action types: <code>wp_option</code>, <code>delete_file</code>, <code>rename_file</code>, <code>file_patch</code>, <code>htaccess_rule</code>, <code>manual</code>.
Hardening Module
Five toggleable hardening rules with clear explanations and compatibility warnings:
<ul>
<li>Disable XML-RPC — blocks external XML-RPC requests and removes X-Pingback header</li>
<li>Hide WordPress Version — removes version leaks from source, RSS feeds, scripts, and styles</li>
<li>Restrict REST API — limits sensitive endpoints to authenticated users</li>
<li>Block Author Scanning — prevents user enumeration via author archives</li>
<li>Login Brute-Force Protection — rate-limits login attempts per IP with configurable thresholds and lockout duration</li>
</ul>
Persistent Findings Store
All audit findings persist in a dedicated database table with automatic deduplication by fingerprint. Track findings over time — dismissed findings stay dismissed across scans; resolved findings reopen if the issue reappears.
Security Event Logging
Every scan, hardening change, remediation, and significant event is logged to a dedicated table. Logs are filterable by severity and exportable as CSV.
WordPress Site Health Integration
Adds 6 security tests to the built-in Site Health screen: file editor, debug mode, XML-RPC, admin username, SSL, and overall security score.
Performance Diagnostics
Built-in performance profiling to identify slow queries, high memory usage, and resource bottlenecks related to security operations.
REST API
10 authenticated endpoints under the <code>aipatch-security-scanner/v1</code> namespace for triggering scans, retrieving summaries, toggling hardening, exporting logs, and running performance diagnostics.
<h4>MCP Surface for AI Agents (23 Abilities)</h4>
Aipatch exposes 23 structured abilities via the WordPress Abilities API — making your site’s security surface fully accessible to external AI agents, coding assistants, and orchestration tools:
By default, only aipatch/audit-site is enabled. You can enable additional abilities from Aipatch Security Scanner -> Settings -> MCP Abilities.
Audit & Scanning
<ul>
<li>aipatch/audit-site — Run a full 36-check security audit with scored findings</li>
<li>aipatch/audit-suspicious — Quick heuristic scan for suspicious files</li>
<li>aipatch/start-file-scan — Launch an async multi-layer malware scan job</li>
<li>aipatch/process-file-scan-batch — Process next batch of files in a running scan</li>
<li>aipatch/file-scan-progress — Check file scan progress</li>
<li>aipatch/file-scan-results — Retrieve enriched scan results with family, reasons, layer scores</li>
<li>aipatch/get-scan-summary — Comprehensive latest scan summary with classification breakdown</li>
<li>aipatch/list-suspicious-files — List suspicious files from latest scan (no job_id needed)</li>
</ul>
Integrity & Baseline
<ul>
<li>aipatch/verify-core-integrity — Verify WP core files against official api.wordpress.org checksums</li>
<li>aipatch/baseline-build — Build or refresh the known-good file hash baseline</li>
<li>aipatch/baseline-diff — Compare current filesystem against stored baseline</li>
<li>aipatch/baseline-stats — Baseline statistics by origin type</li>
<li>aipatch/get-baseline-drift — Combined baseline drift + core integrity report</li>
</ul>
Findings & Monitoring
<ul>
<li>aipatch/list-findings — Query persistent findings with status/severity/category filters</li>
<li>aipatch/findings-stats — Aggregate finding statistics</li>
<li>aipatch/findings-diff — New and resolved findings since a point in time</li>
<li>aipatch/get-file-finding-detail — Single finding with decoded metadata, layer scores, family</li>
<li>aipatch/dismiss-finding — Dismiss a finding as accepted risk</li>
</ul>
Remediation
<ul>
<li>aipatch/apply-remediation — Apply a security fix with rollback support</li>
<li>aipatch/rollback-remediation — Undo a previously applied fix</li>
<li>aipatch/list-remediations — List remediation history with filters</li>
</ul>
Jobs & Status
<ul>
<li>aipatch/list-jobs — List scan/audit jobs with filters</li>
<li>aipatch/get-async-job-status — Check async job status and retrieve results</li>
</ul>
20 abilities are read-only; only 3 (dismiss, apply-remediation, rollback) modify site state. All abilities include typed input/output schemas, permission checks (<code>manage_options</code>), and structured error responses.
<h4>What Aipatch Does NOT Do</h4>
<ul>
<li>It is NOT a firewall or WAF — it does not filter incoming traffic.</li>
<li>It does NOT intercept frontend requests or affect page load performance.</li>
<li>It does NOT phone home, require an account, or send data externally.</li>
<li>It does NOT inject ads, upsells, or nag notices.</li>
</ul>

Aipatch Security Scanner

WordPress security scanner with 36 checks, malware scanning, core integrity verification, remediation, and 23 MCP abilities.

Blueternal BOLT Security Toolkit vs Aipatch Security Scanner