SentinelGuard — Fraud & Checkout Protection for WooCommerce
| 开发者 | mustafizurdev |
|---|---|
| 更新时间 | 2026年8月31日 21:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Card Testing Bots: Hundreds of rapid, small, or failed checkout attempts hitting Stripe, PayPal, or Authorize.Net.
- Fake & Spam Orders: Automated bot checkouts using fake names, sequential numbers, or disposable email addresses.
- High Decline Penalties: Warnings from payment gateways about elevated failure rates threatening your merchant account standing.
- Checkout Script Tampering: Malicious JavaScript or Magecart sniffers attempting to harvest cardholder details on payment forms.
- Stealth Database Backdoors: Rogue administrator accounts created directly in MySQL that stay invisible in the standard WordPress user list.
安装:
- Upload the
sentinelguard-ecommerce-protectionfolder to the/wp-content/plugins/directory. - Activate the plugin through the 'Plugins' menu in WordPress.
- Go to the new SentinelGuard menu to review your security dashboard.
屏幕截图:
常见问题:
Does this replace my firewall (WAF)?
No. SentinelGuard is designed to complement firewalls like Cloudflare or Wordfence. They handle basic perimeter defense, while SentinelGuard handles ecommerce-specific logic (orders, checkouts, payment hooks).
Will this slow down checkout?
No. The pre-gateway checks take milliseconds, and background tasks (like log purging) are scheduled via WP Cron so they don't impact shoppers. Memory footprint is typically under 2MB.
How do I stop WooCommerce card testing bots?
Activate SentinelGuard and leave it in the default Observe mode for a few days to build a baseline of your store's normal checkout traffic. Once you're confident in the findings, switch to active enforcement and it will rate-limit and block card testing patterns before they reach your payment gateway.
Does this detect Magecart and checkout skimmers?
Yes. SentinelGuard continuously scans your frontend scripts, database options, and active theme for the code patterns and keylogger beacons associated with Magecart-style skimmers, and quarantines anything suspicious.
Will this affect my payment gateway fees or decline rate?
No, and it should help. By filtering obvious card testing attempts before they hit Stripe, PayPal, or Authorize.Net, SentinelGuard reduces the failed-authorization volume that drives up processor fees and decline-rate warnings.
Does this work with WooCommerce Blocks and High-Performance Order Storage (HPOS)?
Yes. SentinelGuard is built natively for both the classic checkout and the Cart/Checkout Blocks architecture, and it's fully compatible with HPOS.
Do I need to configure anything, or does it work out of the box?
It works out of the box in Observe mode, recording telemetry with no risk of blocking real customers. Optional integrations like Patchstack, WPScan, and AI-assisted explanations require you to add your own API key in Settings.
更新日志:
- Updated plugin title and tags to lead with WooCommerce for better search visibility.
- Expanded the FAQ with common card testing, skimmer, and HPOS compatibility questions.
- Established Observe-First deployment lifecycle to protect stores against checkout false positives.
- Transitioned quarantine storage completely to the database, eliminating all code file storage on disk.
- Added server-level .htaccess and 0-byte index.php protection guards for quarantine vaults.
- Hardened classic and blocks checkout interception with exception halting to block rogue payment gateway continuation.
- Registered custom 7-day weekly interval for WP-Cron scan scheduling.
- Centralized all content and plugin directory path lookups in SentinelWP_Helper, eliminating direct WP_CONTENT_DIR and WP_PLUGIN_DIR constant access.
- Standardized root path resolution and relative path helpers to use WordPress core APIs instead of internal constants.
- Cleaned up obsolete vault initialization methods and sanitized session journey cookies.
- Synchronized webhook alert configuration and ensured admin assets load across all settings screens.
- Ensured empty index.php directory listing guards in vault and languages directories.
- Standardized plugin directory path resolution with dynamic fallbacks.
- Rebranded to SentinelGuard and updated the plugin slug to sentinelguard-ecommerce-protection.
- Fixed broken "Scan Site Now" button (JS selector mismatch).
- Fixed skimmer and nulled-plugin findings not saving to the database.
- Replaced hardcoded directory paths with plugin_dir_path() and WP_CONTENT_DIR.
- Removed PHP execution headers from quarantine vault files.
- Added quarantine vault cleanup and missing options to uninstall.php.
- Fixed broken Patchstack terms URL and updated Tested up to value.
- Documented all external API services with working Terms and Privacy links.
- Simplified readme description and removed marketing fluff.
- Rebranded to SentinelGuard — Ecommerce & Checkout Protection.
- Updated contributor list and plugin URI.
- Documented all external API services with Terms and Privacy links.
- Simplified readme text.
- Removed AI rate limits to comply with WordPress.org trialware guidelines.
- Updated text domain and branding.
- Improved quarantine safety measures.
- Initial public release.