Description
Defen.so is a developer-first web application security SaaS. This plugin gives your WordPress site real, local protection out of the box, and connects to Defen.so in one click for a managed cloud layer on top — no API key to paste, no config file.
Works standalone — no account required
You do not need a Defen.so account to use the plugin. These features run entirely on your own server, for free, with no sign-up and no limits:
- Upload scanning — every uploaded file is checked for dangerous extensions and polyglots (magic bytes that disagree with the declared type). Runs on every upload for everyone.
- Login hardening — per-IP brute-force rate limiting with adjustable attempt count + window, optional reCAPTCHA v3, optional TOTP 2FA.
- Geo-block — reject requests from any list of countries.
- Local malware scan — heuristic sweep of your PHP/JS files for common webshell / obfuscation patterns.
- File-integrity baseline — snapshot your files and compare for changes.
- Activity log — records the last 100 high-value admin actions locally.
Better when connected (optional)
Connecting a free Defen.so account adds the managed cloud layer — none of it takes anything away from the standalone features above:
- Managed WAF — blocks SQL injection, XSS, path traversal, bot scanners, mass assignment, using the rule set + custom rules from your Defen.so dashboard.
- Attack log + uptime monitor — blocked events (including upload blocks) streamed to your dashboard; edge uptime checks.
- CVE vulnerability lookup — checks your installed plugins/themes against the live CVE feed.
Paid plans (Pro $29/mo, Business $69/mo per site) increase the server-side quotas — monitor interval, log retention, custom-rule count, scan frequency — all of which run on Defen.so infrastructure, not by unlocking code in this plugin.
One-click connect
Click “Connect to Defen.so”. A popup opens at app.defen.so, you sign in (or sign up), authorize the connection, and the popup postMessages a scoped API key back — origin-locked to app.defen.so so no third party can intercept.
Fails-open: if Defen.so is unreachable at request time, the plugin allows the request and ships the log later.
External services
This plugin connects to external services. Here is exactly what is sent, when, and to whom.
1. Defen.so API (app.defen.so) — the plugin’s core service.
- What it is: the managed WAF, uptime monitoring, and attack-log backend the plugin connects your site to.
- When data is sent: when you connect your site (one-time OAuth handshake), when the plugin refreshes its cached rule policy, and when a request is blocked/challenged/deceived (attack-log events are batched and sent on
shutdown). - What is sent: your scoped API token, your site URL, and per-event metadata — HTTP method, URL path, visitor IP, User-Agent, matched rule ID, and the action taken. No request bodies, no cookies, no personal content.
- Terms: https://defen.so/tos — Privacy: https://defen.so/privacy
2. Google reCAPTCHA (google.com/recaptcha) — optional, only if you enable login hardening with a reCAPTCHA site key.
- What it is: Google’s bot-detection service, used to score login attempts on
wp-login.php. - When data is sent: only on the login page, and only if you have entered a reCAPTCHA site key in the plugin settings. If you leave it blank, no request is ever made to Google.
- What is sent: the reCAPTCHA token and the data Google’s script collects from the login page (per Google’s terms).
- Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy
3. ip-api.com — optional, only if you enable the geo-block feature.
- What it is: a free IP-to-country geolocation lookup, used to find the country of a visitor so the geo-block rule can allow or deny it.
- When data is sent: only when geo-block is enabled and a visitor’s country is not already supplied by your host (e.g. Cloudflare’s country header). The visitor’s IP address is sent for the lookup.
- What is sent: the visitor’s IP address only.
- Terms: https://ip-api.com/docs/legal — Privacy: https://ip-api.com/docs/legal
Installation
- Upload
defen-so-connectorto/wp-content/plugins/. - Activate through the “Plugins” menu.
- You’ll be redirected to the Defen.so setup page. Click “Connect to Defen.so” and follow the popup.
FAQ
-
Does the plugin slow down my site?
-
No. The WAF check on
initreads a locally-cached policy (10-min TTL, stale-while-revalidate) — no external HTTP call on the hot path. Attack logs ship in a batched, non-blockingwp_remote_postonshutdown. -
What happens if Defen.so is down?
-
Fails open. The cached policy stays live for 24 h so protection continues even during an outage. If the cache is also gone, requests are allowed.
-
Is my data safe?
-
Only attack-log metadata leaves your site: method, URL path, IP, User-Agent, matched rule ID, action. No request bodies, no cookies, no PII.
-
Can I self-host?
-
Not today. The plugin is the SDK; the classifier, rule store, and dashboard live on Defen.so infra.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Defen.so Connector” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “Defen.so Connector” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.8
- Plugin URI updated to the plugin’s page (previous URL now redirects).
- No functional changes from 1.1.7.
1.1.7
- All local tools (malware scan, file integrity, vulnerability listing UI, geo-block, login hardening, activity log) now render and work without connecting an account, per directory Guideline 5. Connection only adds the external Defen.so service (WAF policy, uptime, attack log, CVE lookups), documented per Guideline 6.
- Admin menu slug renamed from defen-so to defenso for a consistent unique prefix.
1.1.6
- Sanitize REQUEST_URI and QUERY_STRING with sanitize_text_field() on receipt; raw copies are used only for in-memory WAF pattern matching, never stored.
1.1.5
- Upload scanning (dangerous extensions + polyglot detection) now runs for everyone, always — it no longer required a connected account, since it’s fully local.
- Sanitized the request path before it’s stored in the local attack-log queue.
- Fixed the Plugin URI and readme Terms link; documented the optional ip-api.com geo-lookup service.
1.1.4
- Plugin Check: set an explicit version arg on the reCAPTCHA script enqueue (false, since Google hosts it) to silence the MissingVersion warning.
1.1.3
- Plugin Check cleanup: reCAPTCHA now loads via wp_enqueue_script; prefixed admin-view variables; trimmed tags to 5; documented the WAF’s raw-input reads.
1.1.2
- Compatibility: tested up to WordPress 7.0.
- Housekeeping: shortened the plugin name so the text domain matches the slug.
1.1.1
- All in-plugin features (login hardening, geo-block, local malware scan, file-integrity, activity log) now work fully for everyone, with no account and no plan limits. Plan tiers only affect the optional server-side cloud services.
- Every AJAX handler now verifies a nonce; sanitized all request/server inputs.
- Documented external services (Defen.so API, optional Google reCAPTCHA) in the readme.
1.1.0
- Added login hardening, geo-block, file-integrity, activity log, and vulnerability + malware scanning modules.
- Cleaner admin page and connect flow.
1.0.0
- Initial release. WAF, upload scan, brute-force signal, uptime monitor, attack log.
