Title: Gatewarden Author: Tudor Constantin Published: 15 ກໍລະກົດ 2026 Last modified: 17 ກໍລະກົດ 2026 --- ຄົ້ນຫາປລັກອິນ ![](https://ps.w.org/gatewarden/assets/banner-772x250.jpg?rev=3609002) ![](https://ps.w.org/gatewarden/assets/icon-256x256.jpg?rev=3609002) # Gatewarden ໂດຍ [Tudor Constantin](https://profiles.wordpress.org/tud0r/) [ດາວໂຫຼດ](https://downloads.wordpress.org/plugin/gatewarden.1.1.0.zip) * [ລາຍລອຽດ](https://lo.wordpress.org/plugins/gatewarden/#description) * [ການຣີວິວ](https://lo.wordpress.org/plugins/gatewarden/#reviews) * [ການຕິດຕັ້ງ](https://lo.wordpress.org/plugins/gatewarden/#installation) * [ການພັດທະນາ](https://lo.wordpress.org/plugins/gatewarden/#developers) [ການຊ່ວຍເຫຼືອ](https://wordpress.org/support/plugin/gatewarden/) ## ຄຳອະທິບາຍ Gatewarden provides a modular security and mail-delivery layer for WordPress and WooCommerce. The interface and source strings are written in English and are translation- ready through the `gatewarden` text domain. All public protection, integration, event-logging, notification, SMTP, and uninstall- cleanup modules are disabled by default. Administrators enable only the features required by the site. The suggested privacy-policy text and WordPress personal-data exporter/eraser integrations are registered while the plugin is active; they only operate on Gatewarden data that actually exists. #### CAPTCHA providers * Google reCAPTCHA v2. * Google reCAPTCHA v3. * Cloudflare Turnstile. #### WordPress protection * Login. * Registration. * Lost password. * Password reset. * Comments. #### WooCommerce protection * My Account login and registration. * Lost-password and reset-password forms. * Checkout login. * Account creation during classic checkout. * Account creation during Checkout Block checkout. #### Security, observability, and email features * Configurable failed-login limits by IP address, username, or IP address and username. * Progressive lockout durations with a configurable multiplier and maximum duration. * Optional neutral account messages for login, registration, and password-recovery flows. * One indexed, retention-aware audit stream with focused Authentication, CAPTCHA, Account activity, and Email views. * Searchable, filterable, sortable, paginated, clearable, and CSV-exportable activity logs. * WordPress-native list tables with Screen Options for visible columns and rows per page. * Human-readable event details instead of raw JSON in the administration interface and CSV exports. * A Gatewarden dashboard with login, lockout, CAPTCHA, email, provider, integration, and recent-event metrics. * A compact WordPress Dashboard widget for administrators. * Optional email alerts for selected lockouts, logins, registrations, password events, CAPTCHA service errors, and SMTP failures. * Asynchronous alert delivery with configurable recipients, successful-login scope, minimum lockout duration, durable deduplication, global rate limits, and duplicate- alert cooldown. * Optional approximate IP location from server headers or an explicit IPWHOIS.io lookup. * Optional standard SMTP delivery with sender, host, port, encryption, authentication, timeout, certificate verification, settings-page secret redaction, and a test tool. * Credential-redacted SMTP diagnostics that classify DNS, connection, timeout, TLS, authentication, relay, sender, recipient, and message-policy failures. * SMTP outcome logging that excludes message bodies, attachments, passwords, and complete recipient addresses. * Configurable log retention and optional data removal on uninstall. * Secret-key and SMTP-password controls that never render a stored secret in administration HTML. * Responsive CAPTCHA wrappers for WordPress and WooCommerce forms. Gatewarden stores security events, lockout state, and pending notification jobs in site-prefixed custom database tables created through the WordPress database API. Records can include IP addresses, submitted usernames, and a WordPress user ID when one is known. Notification payloads are removed after terminal processing, deduplication hashes are cleared after the maximum cooldown, and obsolete queue records are cleaned automatically. Configure event logging, alerting, and retention according to the site’s privacy and operational requirements. To disable public Gatewarden protection during an emergency, add this to `wp-config. php`: ``` define( 'GATEWARDEN_DISABLE', true ); ``` Administrators with the `manage_options` capability see a warning while the emergency bypass is active. The default allowed CAPTCHA verification hostnames are the normalized hosts from` home_url()` and `site_url()`. Additional explicit hostnames can be supplied through the `gatewarden_allowed_hostnames` filter. #### Developer and infrastructure controls Gatewarden provides narrowly scoped filters for installations that need infrastructure or integration-specific policy. Treat them as code-level controls and validate all values returned by custom callbacks. * Authentication: `gatewarden_limit_authentication_request` can exclude a classified channel/request; `gatewarden_invalid_credential_error_codes` changes the credential- error allowlist; the legacy `gatewarden_is_interactive_login_request` filter remains available for form detection. * Client IP: `gatewarden_trusted_proxy_ranges` declares trusted proxy addresses/ CIDRs and `gatewarden_client_ip` can override the final validated address. Forwarded headers are ignored unless the socket peer is trusted. * CAPTCHA hostname verification: `gatewarden_allowed_hostnames` changes the strict hostname allowlist. * SMTP scope and network policy: `gatewarden_smtp_apply_to_mail` can opt an individual PHPMailer transaction out of Gatewarden SMTP. Private/reserved SMTP destinations on multisite require `GATEWARDEN_ALLOW_PRIVATE_SMTP_HOST` or `gatewarden_allow_private_smtp_host`; authenticated SMTP without transport encryption requires `GATEWARDEN_ALLOW_INSECURE_SMTP_AUTH` or `gatewarden_allow_insecure_smtp_auth`. * Notification capacity: `gatewarden_notification_queue_max`, `gatewarden_notification_queue_total_max`,` gatewarden_notification_limit_per_minute`, `gatewarden_notification_limit_per_hour`,` gatewarden_notification_batch_size`, `gatewarden_notification_max_attempts`, and `gatewarden_notification_lease_seconds` adjust bounded worker limits. * Notification content: `gatewarden_notification_recipients`, `gatewarden_notification_subject`,` gatewarden_notification_message`, and `gatewarden_ip_location` receive sanitized notification context. * CSV export: `gatewarden_csv_export_max_rows` changes the bounded export safety limit. Operational integrations can observe `gatewarden_event_recorded`, `gatewarden_login_limit_error`,` gatewarden_notification_dropped`, `gatewarden_notification_capture_exception`, ` gatewarden_notification_worker_exception`, `gatewarden_notification_resume_exception`,` gatewarden_notification_exception`, `gatewarden_smtp_test_completed`, `gatewarden_smtp_mailer_configured`,` gatewarden_smtp_configuration_failed`, `gatewarden_smtp_configuration_exception`,` gatewarden_smtp_sender_error`, and `gatewarden_privacy_tool_error`. ``` gatewarden_login_limit_error receives `(string $message, WP_Error $error)`. `gatewarden_notification_worker_exception` always receives `(Throwable $error, ?array $claimed_row)`, with `null` for a batch-level failure. `gatewarden_notification_exception` receives `(Throwable $error, array $event)` when mail delivery or its cleanup raises an exception inside the worker boundary. `gatewarden_smtp_mailer_configured` receives the live PHPMailer object and a settings array whose `password` value is empty and whose `password_configured` flag reports whether a password exists. The live PHPMailer object is privileged and can itself contain the configured password, so callbacks must never log or expose it. Observer callbacks should remain fast; Gatewarden contains exceptions from authentication and notification diagnostic observers, but integrations should not deliberately throw. ``` ### External services Gatewarden connects to an external service only after the relevant feature is explicitly configured and enabled by an administrator, or when an administrator explicitly runs the SMTP connection test with complete SMTP settings. #### Google reCAPTCHA When Google reCAPTCHA v2 or v3 is selected, Gatewarden loads Google’s reCAPTCHA JavaScript from `www.google.com` on protected forms and sends the generated response token and configured secret key to Google’s verification endpoint. Gatewarden does not include the visitor’s IP address in the server-side verification request. Google’s client-side service may process browser and device data under Google’s terms. * Service: https://www.google.com/recaptcha/about/ * Privacy policy: https://policies.google.com/privacy * Terms: https://policies.google.com/terms #### Cloudflare Turnstile When Cloudflare Turnstile is selected, Gatewarden loads the Turnstile JavaScript from `challenges.cloudflare.com` on protected forms and sends the generated response token and configured secret key to Cloudflare’s verification endpoint. Gatewarden does not include the visitor’s IP address in the server-side verification request. Cloudflare’s client-side service may process browser and device data under Cloudflare’s policies. * Service: https://www.cloudflare.com/products/turnstile/ * Privacy policy: https://www.cloudflare.com/privacypolicy/ * Terms: https://www.cloudflare.com/website-terms/ #### Administrator-configured SMTP server When SMTP is enabled, WordPress sends outgoing message content, recipient addresses, and sender details to the SMTP server configured by the administrator. The server may be operated by any provider selected by the site owner. Gatewarden stores the configured SMTP password in the WordPress options table, never renders the stored password in administration HTML, and supplies it only to the configured host during SMTP authentication. Review the selected provider’s privacy policy and terms before enabling SMTP. #### IPWHOIS.io Approximate location is disabled by default. When an administrator enables location in security notifications and explicitly selects IPWHOIS.io, Gatewarden sends the event IP address to `ipwho.is` and requests country, region, and city data. The result is cached on the WordPress site for 24 hours. Server-header location mode does not make this external request. * Service and documentation: https://ipwhois.io/documentation * Privacy policy: https://ipwhois.io/privacy * Terms: https://ipwhois.io/terms ## ການຕິດຕັ້ງ 1. Upload the `gatewarden` directory to `/wp-content/plugins/`, or install the ZIP from Plugins > Add New Plugin > Upload Plugin. 2. Activate Gatewarden. 3. Open the top-level Gatewarden menu. 4. Enable and configure only the required modules. No public protection is active until it is explicitly enabled. ## ຄຳຖາມທີ່ພົບເລື້ອຍ ### Is any protection enabled immediately after activation? No. CAPTCHA protection, protected forms, login limits, WooCommerce integration, generic account messages, event logging, notifications, SMTP, and uninstall cleanup are disabled by default. ### Can login limits run without CAPTCHA? Yes. Login limits have their own activation control and do not require a configured CAPTCHA provider. ### What do generic account messages change? When enabled, Gatewarden replaces account-specific login and registration errors with neutral messages. Password-recovery requests for known and unknown accounts use the same public confirmation message, while an email is sent only for a real account. CAPTCHA and lockout errors remain authoritative. ### Why does Gatewarden keep one log table instead of one table per subsystem? Authentication, CAPTCHA, account, and email events share the same retention, export, search, and dashboard requirements. One indexed audit schema avoids duplicated maintenance logic and supports cross-category investigation. It is intentionally not append- only: configured retention, administrative clearing, uninstall cleanup, and WordPress personal-data erasure can delete or anonymize records. The administration screen separates the data into native category views so unrelated records do not have to be displayed together. ### What SMTP information is stored in logs? When event logging and SMTP are enabled, Gatewarden records whether the WordPress mail transaction was accepted or failed, the SMTP host, port, encryption mode, recipient count, recipient domains, attachment count, and a sanitized failure reason. It does not store email bodies, attachment contents or paths, SMTP credentials, or complete recipient addresses. ### Where can I see the exact SMTP test failure? After a test, Gatewarden displays the latest result for the current administrator on the SMTP tab for up to seven days. The report includes the exact sanitized mail error, an actionable classification, connection settings, elapsed time, and a bounded SMTP transcript with credentials and AUTH payloads redacted. Scheduled deletion uses WordPress Cron, so disabled or delayed cron can postpone physical removal; an expired report is also removed when it is next accessed. It does not depend on` debug.log`. ### Does a successful SMTP test guarantee inbox delivery? No. A successful result means the WordPress mail transport accepted the message. Final delivery can still be affected by provider policy, spam filtering, DNS authentication, mailbox rules, or downstream delivery failures. Review the provider delivery logs when a message is accepted but does not arrive. ### Can notifications create an email loop when SMTP is broken? No. Notification delivery failures are recorded as email events when logging is enabled, but they do not trigger another SMTP-failure notification. Potentially noisy alert types also support a configurable cooldown. ### Are security notifications delivered immediately? Not necessarily. Public requests only enqueue eligible alerts; a bounded WordPress Cron worker performs optional external geolocation and email delivery later. On low-traffic sites or sites with WP-Cron disabled, delivery, retries, stale-job recovery, and cleanup can be delayed. Configure a real system cron to run WordPress scheduled events when predictable timing is required. Login, registration, comments, and checkout do not wait for those network operations. ### Does Gatewarden SMTP apply only to Gatewarden alerts? No. When enabled, Gatewarden configures WordPress’s shared PHPMailer transport, so it normally applies to all `wp_mail()` messages. `gatewarden_smtp_apply_to_mail` can opt individual transactions out or return false for every message when another transport owns delivery. Gatewarden reports any other `phpmailer_init` callback without executing or identifying it, but it cannot infer that callback’s behavior or guarantee coexistence with every SMTP plugin; use one transport owner or test an explicit integration policy. ### Does the emergency bypass disable login limits too? Yes. When `GATEWARDEN_DISABLE` is strictly `true`, public CAPTCHA checks, login- limit enforcement, and generic account-message rewriting are bypassed. Administration, migrations, SMTP, logging, notifications, stored settings, and existing data remain available. ### Are stored secret keys or SMTP passwords rendered in the settings page? No. Existing values are never included in the HTML. They can be retained, explicitly replaced, or deleted. The SMTP password is stored in the WordPress options table; Gatewarden does not claim application-level encryption at rest. Protect database access and backups as credentials. ### How do the WordPress personal-data tools handle security records? Gatewarden registers native exporters and erasers for audit events, the matching user’s latest SMTP diagnostic, and still-deliverable notification payloads. Event and queue exports use bounded keyset pages with the maximum existing ID captured on the first page and an expiring 24-hour cursor, so later inserts cannot expand an in-progress export and concurrent deletions cannot shift unread rows past an offset. This is not a transactional snapshot: data removed, anonymized, or terminalized before its page is read is no longer available, and an expired or invalid cursor requires restarting the export. Automatic matching is deliberately limited to a stored WordPress user ID. A submitted username or email address alone is not proof that the request came from that person, so Gatewarden does not expose an attacker’s IP or event merely because the attacker typed someone else’s identifier. Erasure removes or anonymizes the reliable association while retaining non-identifying security evidence where appropriate. ### What happens to data on uninstall? By default, settings and security tables are retained. Enable the uninstall data- removal option in Gatewarden > Settings to remove the site’s settings, tables, list preferences, and recent SMTP diagnostic metadata when the plugin is uninstalled. ## ການຣີວິວ ບໍ່ມີການຣີວິວສຳລັບປລັກອິນນີ້. ## ຜູ້ຮ່ວມພັດທະນາ ແລະ ຜູ້ພັດທະນາ “Gatewarden” ແມ່ນຊອຟແວໂອເພັນຊອດ (Open Source). ບຸກຄົນຕໍ່ໄປນີ້ໄດ້ມີສ່ວນຮ່ວມໃນການພັດ ທະນາປລັກອິນນີ້. ຜູ້ຮ່ວມພັດທະນາ * [ Tudor Constantin ](https://profiles.wordpress.org/tud0r/) [ແປ “Gatewarden” ເປັນພາສາຂອງເຈົ້າ.](https://translate.wordpress.org/projects/wp-plugins/gatewarden) ### ສົນໃຈຮ່ວມພັດທະນາບໍ່? [ເບິ່ງລະຫັດ](https://plugins.trac.wordpress.org/browser/gatewarden/), ກວດເບິ່ງ [ຄັງເກັບ SVN](https://plugins.svn.wordpress.org/gatewarden/), ຫຼື ຕິດຕາມ [ບັນທຶກການພັດທະນາ](https://plugins.trac.wordpress.org/log/gatewarden/) ຜ່ານ [RSS](https://plugins.trac.wordpress.org/log/gatewarden/?limit=100&mode=stop_on_copy&format=rss). ## ບັນທຶກການປ່ຽນແປງ #### 1.1.0 * Extended login-limit coverage to compatible WordPress authentication channels, including nested XML-RPC and Application Password flows, while counting only confirmed invalid-credential errors and preserving explicit integration filters. * Reworked schema migrations to serialize upgrades and verify required tables, columns, indexes, InnoDB engines, and bounded backfills before recording schema version 1.3.0, with visible operational failures and safe retries. * Moved security-notification delivery and optional external geolocation to a bounded WordPress Cron queue with durable deduplication, per-minute/hour limits, unique leases, cooldowns, capped retries, fatal/stale-job recovery, terminal-payload removal, cleanup, and complete cron unscheduling on deactivation/uninstall. * Added trusted-proxy validation for forwarded IP and geolocation headers. CAPTCHA hostname verification now accepts the normalized `home_url()` and `site_url()` hosts by default. * Hardened multisite SMTP destinations against private/reserved addresses and DNS rebinding by validating A/AAAA answers and pinning connections while retaining the TLS peer name. Authentication over an unencrypted transport now requires explicit opt-in. * Isolated SMTP configuration exceptions from `wp_mail()`, added per-message transport opt-out, bounded diagnostics, conflict reporting, and opportunistic expiry when WordPress Cron is delayed. * Batched log retention and clearing with monotonic checkpoints, and changed CSV export to a bounded maximum-ID range so concurrent events cannot extend the exported record set. * Added native WordPress personal-data exporters and erasers for reliably linked audit events, SMTP diagnostics, and pending notifications without treating a submitted username/email as proof of identity. Event and queue exports use bounded keyset cursors with a captured maximum-ID boundary and 24-hour transient state. * Hardened WooCommerce Store API protection for direct and batch Checkout requests, required-account registration, generic account responses, and official extension- data schema; declared HPOS compatibility without accessing order storage. * Switched reCAPTCHA v2 to explicit, idempotent rendering so multiple and dynamically inserted protected forms receive their own widget. * Stabilized login-limit and notification-worker diagnostic hook signatures, isolated their observers from protected requests and queue recovery, and redacted the settings array passed to the SMTP configured hook. * Split administration queries, data preparation, tab renderers, asset loading, and component CSS while retaining existing hooks, option keys, nonces, filters, selectors, and cascade order. * Converted data-changing administration links to nonce-protected POST actions, corrected administrative ARIA state handling, and kept Gatewarden assets scoped to its own screens. * Added a capability-checked Settings action on the Plugins screen that opens the Gatewarden Dashboard. * Added native Gatewarden submenus for direct Dashboard, CAPTCHA and providers, Login limits, Logs, Notifications, SMTP, Integrations, and Settings navigation from one centralized tab registry. * Corrected the shared administration-button loading component with a visible centered spinner, stable dimensions, accessible busy state, cancellation recovery, and finite download handling. * Integrated Checkout Blocks with the official checkout-validation event for standard and express methods participating in the Blocks event cycle, retaining a guarded standard-button fallback and authoritative direct/batch Store API validation. * Removed the long-lived repeatable-read CSV transaction while preserving streaming cursor batches, filters, the captured maximum-ID boundary, row limits, and spreadsheet- formula neutralization. * Generalized SMTP conflict detection to every foreign phpmailer_init callback, with credential-free administrator warnings and documented per-message or complete transport opt-out through gatewarden_smtp_apply_to_mail. #### 1.0.0 * Initial public release. * Production-ready, WordPress-native administration UI with responsive navigation, full-width controls, consistent Dashicon statuses, accessible focus states, Screen Options support, and tablet/mobile list-table presentation. * CAPTCHA protection with Google reCAPTCHA v2, Google reCAPTCHA v3, and Cloudflare Turnstile for supported WordPress and WooCommerce forms. * Progressive login limits by IP address, username, or both, including configurable lockout escalation and active-lockout management. * Categorized security activity logs with search, filters, sorting, pagination, Screen Options, CSV export, and retention controls. * Security metrics in the Gatewarden dashboard and a compact WordPress Dashboard widget. * Optional generic account messages that reduce account-enumeration information in login, registration, and password-recovery flows. * Optional SMTP delivery with settings-page secret redaction, connection testing, actionable diagnostics, and mail outcome logging. * Configurable email notifications for selected authentication, lockout, account, CAPTCHA, and SMTP events. * Privacy guidance, translation support, accessible administration controls, WooCommerce integration, and optional uninstall cleanup. * CAPTCHA protection, login limits, logging, notifications, SMTP, integrations, and data removal remain disabled until explicitly enabled by an administrator. ## ຂໍ້ມູນກຳກັບ (Meta) * ເວີຊັນ **1.1.0** * ອັບເດດຫຼ້າສຸດເມື່ອ **5 ມື້ ທີ່ຜ່ານມາ** ທີ່ຜ່ານມາ * ການຕິດຕັ້ງທີ່ໃຊ້ງານຢູ່ **ໜ້ອຍກວ່າ 10** * ເວີຊັນ WordPress ** 6.5 ຫຼື ສູງກວ່າ ** * ທົດສອບເຖິງເວີຊັນ **7.0.2** * ເວີຊັນ PHP ** 8.0 ຫຼື ສູງກວ່າ ** * ພາສາ * [English (US)](https://wordpress.org/plugins/gatewarden/) * ແທັກ * [captcha](https://lo.wordpress.org/plugins/tags/captcha/)[login security](https://lo.wordpress.org/plugins/tags/login-security/) [security](https://lo.wordpress.org/plugins/tags/security/)[smtp](https://lo.wordpress.org/plugins/tags/smtp/) [woocommerce](https://lo.wordpress.org/plugins/tags/woocommerce/) * [ມຸມມອງຂັ້ນສູງ](https://lo.wordpress.org/plugins/gatewarden/advanced/) ## ການໃຫ້ຄະແນນ ຍັງບໍ່ມີການສົ່ງຄຳວິຈານເທື່ອ. [Your review](https://wordpress.org/support/plugin/gatewarden/reviews/#new-post) [ເບິ່ງ ຄຳຄິດເຫັນ ທັງໝົດ](https://wordpress.org/support/plugin/gatewarden/reviews/) ## ຜູ້ຮ່ວມພັດທະນາ * [ Tudor Constantin ](https://profiles.wordpress.org/tud0r/) ## ການຊ່ວຍເຫຼືອ ມີຄຳຖາມ ຫຼື ຕ້ອງການຄວາມຊ່ວຍເຫຼືອບໍ່? [ເບິ່ງຟໍຣັມການຊ່ວຍເຫຼືອ](https://wordpress.org/support/plugin/gatewarden/)