Aipatch Security Scanner
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. Why Aipatch Security Scanner? Most WordPress security plugins are either too simple to be useful or too heavy to be practical. Aipatch takes a different approach: Audit-first architecture. Every check is a standalone, testable module that returns structured findings with severity, confidence, evidence, and fingerprints. 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. Zero external dependencies. Everything runs locally. No accounts, no cloud services, no API keys required. Reversible by design. Every automated remediation stores rollback data so you can undo any change with one click. Core Capabilities 36-Point Security Audit Aipatch runs 36 automated checks across 8 categories — core, plugins, themes, users, configuration, server, access control, and malware surface: Outdated WordPress core, plugins, and themes Default admin username, excessive admin accounts, inactive admin users, user ID 1 exposure XML-RPC, file editor, debug mode, debug log, REST API exposure, directory listing PHP version, HTTPS, file permissions, security headers (X-Frame-Options, CSP, etc.) Database prefix, sensitive files, PHP execution in uploads, auto-update configuration Salt key strength, cron health, cookie security flags, CORS, application passwords Exposed backup files, phpinfo files, uploads directory indexing, default login URL Database credential security, file installation permissions 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: Code execution patterns: eval(), assert(), create_function(), preg_replace /e System command functions: shell_exec, exec, passthru, backtick operators Obfuscation techniques: base64 encoding, hex encoding, str_rot13, gzinflate chains, chr() concatenation, variable variables, suspiciously long lines Network/exfiltration: cURL execution, fsockopen, remote file_get_contents Known backdoor signatures: c99, r57, WSO, b374k, weevely, FilesMan WordPress-specific threats: unauthorized admin creation, critical option injection, security function removal 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: wp_option, delete_file, rename_file, file_patch, htaccess_rule, manual. Hardening Module Five toggleable hardening rules with clear explanations and compatibility warnings: Disable XML-RPC — blocks external XML-RPC requests and removes X-Pingback header Hide WordPress Version — removes version leaks from source, RSS feeds, scripts, and styles Restrict REST API — limits sensitive endpoints to authenticated users Block Author Scanning — prevents user enumeration via author archives Login Brute-Force Protection — rate-limits login attempts per IP with configurable thresholds and lockout duration 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 aipatch-security-scanner/v1 namespace for triggering scans, retrieving summaries, toggling hardening, exporting logs, and running performance diagnostics. MCP Surface for AI Agents (23 Abilities) 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 aipatch/audit-site — Run a full 36-check security audit with scored findings aipatch/audit-suspicious — Quick heuristic scan for suspicious files aipatch/start-file-scan — Launch an async multi-layer malware scan job aipatch/process-file-scan-batch — Process next batch of files in a running scan aipatch/file-scan-progress — Check file scan progress aipatch/file-scan-results — Retrieve enriched scan results with family, reasons, layer scores aipatch/get-scan-summary — Comprehensive latest scan summary with classification breakdown aipatch/list-suspicious-files — List suspicious files from latest scan (no job_id needed) Integrity & Baseline aipatch/verify-core-integrity — Verify WP core files against official api.wordpress.org checksums aipatch/baseline-build — Build or refresh the known-good file hash baseline aipatch/baseline-diff — Compare current filesystem against stored baseline aipatch/baseline-stats — Baseline statistics by origin type aipatch/get-baseline-drift — Combined baseline drift + core integrity report Findings & Monitoring aipatch/list-findings — Query persistent findings with status/severity/category filters aipatch/findings-stats — Aggregate finding statistics aipatch/findings-diff — New and resolved findings since a point in time aipatch/get-file-finding-detail — Single finding with decoded metadata, layer scores, family aipatch/dismiss-finding — Dismiss a finding as accepted risk Remediation aipatch/apply-remediation — Apply a security fix with rollback support aipatch/rollback-remediation — Undo a previously applied fix aipatch/list-remediations — List remediation history with filters Jobs & Status aipatch/list-jobs — List scan/audit jobs with filters aipatch/get-async-job-status — Check async job status and retrieve results 20 abilities are read-only; only 3 (dismiss, apply-remediation, rollback) modify site state. All abilities include typed input/output schemas, permission checks (manage_options), and structured error responses. What Aipatch Does NOT Do It is NOT a firewall or WAF — it does not filter incoming traffic. It does NOT intercept frontend requests or affect page load performance. It does NOT phone home, require an account, or send data externally. It does NOT inject ads, upsells, or nag notices.
Ordlo Catalog Audit
Bad catalogue data doesn’t show on the shop front. It shows up in disapproved Google Shopping feeds, unindexed product pages, cart drop-offs on missing weights, and the support tickets that follow. Ordlo Catalog Audit scans your WooCommerce product catalogue in a single pass and surfaces the data quality issues that quietly cost you sales: missing SKUs, missing GTIN/UPC/EAN/ISBN barcodes, missing or zero prices, empty descriptions, missing weights, missing images, missing brands, duplicate identifiers and broken/orphaned variations. The full audit is free. Detect every issue here, fix them by hand in the WooCommerce editor, or upgrade to Ordlo Catalog Audit Pro to resolve issues one click at a time or in bulk without leaving the audit screen. What it checks Every check runs in the same scan. There’s nothing to configure first — the audit reads what WooCommerce already stores and flags what’s missing or wrong. Missing SKU – Published products and variations with an empty SKU. Variable parents and grouped products are excluded; they don’t carry SKUs by design. Duplicate SKU – Two or more products sharing the same SKU value. Fulfilment, picking and feed exports all assume SKUs are unique. Missing GTIN / UPC / EAN / ISBN – Products with no barcode identifier set. Google Shopping requires this for most categories, and missing GTINs are a common feed rejection cause. Duplicate GTIN / UPC / EAN / ISBN – Products sharing the same barcode value. WooCommerce requires this identifier to be globally unique. Missing featured image – Products with no featured image, which appears in catalogue pages, cart line items, Shopping feeds and most theme product cards. Missing product brand – Products with no product_brand term assigned. Runs only when WooCommerce Brands (or a compatible product_brand taxonomy) is active. Missing price – Simple and external products with no regular price. WooCommerce won’t add them to the cart and they’re invisible in feed exports. Zero price – Products priced at 0.00 that may be unintentional. Empty description – Products missing the long description. Empty short description – Products missing the short description that sits above the add-to-cart button in most themes. Missing weight – Non-virtual products with no weight configured. Empty weights silently break shipping rate plugins and label printing. Orphaned variations – Variation records whose parent product is missing – invisible to customers, but a problem once reports start counting products. Plus expanded image checks (missing variation images, missing alt text, broken featured images, thin galleries), expanded catalogue checks (duplicate titles, missing categories, uncategorized-only products, external products without URLs, visible out-of-stock items) and variation configuration checks (missing variation prices, missing managed stock quantities, inconsistent attributes, incomplete variable parents). More than a checklist Catalog health score – A dashboard score weighted by open-issue severity and catalogue size, with a health trend over time. Channel & integration readiness – Free readiness scoring for Google Shopping, Meta Commerce, marketplace identifiers and fulfilment/API integrations, with the blockers listed per channel. Per-channel blocker export – Download a CSV of the blockers and warnings for any channel straight from the dashboard. Optional MPN audit – Configurable manufacturer part number checks for marketplace readiness. Feed plugin detection – Recognises Google Listings & Ads, Facebook for WooCommerce, CTX Feed and Product Feed Pro. How it works Install the plugin. The audit lives under Ordlo → Catalog Audit. There’s no setup wizard and no required configuration. Click Run Full Audit. The plugin scans your catalogue in the background, paginated so it doesn’t time out on large stores. Browse the issues. Each check has its own tab with a count badge and a table of affected products. Click a row to open the WooCommerce editor. Mark issues as Resolved or Ignore to keep the dashboard honest, then re-run the audit to confirm they’re cleared. A first pass on a typical thousand-product store takes about a minute, and re-runs after a fix session take the same. Free vs Pro The detection layer is the whole audit, free here on WordPress.org. The fix layer is what Pro adds. Included in the free plugin: The full audit across every check above. Per-check issue tabs with counts and filters. Catalog health score and health trend. Channel & integration readiness scoring with per-channel blocker CSV export. Optional MPN audit and feed plugin detection. Direct link to the WooCommerce editor for each issue. Mark as Resolved / Ignore, and re-run on demand. Settings to enable or disable individual audit types. Ordlo Catalog Audit Pro adds the fixes: One-click Fix per issue (SKU, GTIN/UPC/EAN/ISBN, price, weight, descriptions, featured image and brand). Bulk Fix All for a single check at once. Auto-generate SKUs from a configurable pattern, with collision checks. Assign a placeholder image or a default weight in bulk. Delete All Orphaned Variations in one go. CSV import for offline batch fixes. Priority email support. Free is permanent – no expiry, no nag. Pro is a separate plugin you install alongside the free one. Built for real stores Reads native WooCommerce data – no schema changes. HPOS-ready (WooCommerce High-Performance Order Storage compatible). Works with WooCommerce 8.0+.
