Request inspection
SQL injection, cross-site scripting, path traversal, file inclusion, code injection and object injection are recognised and refused.
Launch offer: one site free for the first 1,000 customers.
Features
Grosfort covers requests, sign-ins, files, the database, the pages your visitors see and the comments they leave.
Firewall
The firewall runs as soon as plugins load, and can be set to run before every other plugin.
SQL injection, cross-site scripting, path traversal, file inclusion, code injection and object injection are recognised and refused.
Scanners such as sqlmap, Nikto and Nuclei are refused by name, and addresses that probe for weaknesses are blocked.
An address that sends far too many requests is blocked for a while.
Addresses that request backup files and known vulnerable paths are blocked after repeated attempts.
Uploaded files, and plugin and theme archives, are inspected for malicious code before they are stored.
An address that attacks at least two unrelated Grosfort customers is blocked for every customer.
Always allow or always block an address or a network, on one site or on all your sites at once.
Verified search engines are never blocked by a country rule or the shared list.
Watch what the firewall would block before you let it block.
Country rules
Block or allow whole countries and whole continents. Apply a rule to the entire site, or only to wp-admin and the login page, so visitors everywhere can read while only your countries can sign in.
The address ranges come from Grosfort's own country table, compiled from the records of the five regional internet registries and checked on your own server.
Scanner
Scans run on the schedule you choose, in short steps, so the site stays responsive.
WordPress, plugins and themes are compared with their official releases.
Changed and unknown files are read for the techniques malware uses: hidden code, disguised function names, data sent to places it should not go.
Files the scan cannot clear are checked by the Grosfort analysis engine against about 5,800 patterns and reviewed samples.
Open any flagged file with the suspicious lines marked, and compare it with the original side by side.
Move a file out of harm's way, or replace it with the verified official version, in one click. A copy is always kept.
Injected scripts, rogue administrators and suspicious database triggers.
Backups, logs and version-control folders anyone could download.
Your pages as visitors and search engines receive them: hidden links, cloaking, redirects, foreign forms and frames.
Every component you run, checked daily against known vulnerabilities, with the fixed version named.
Compare
A finding that says “this file was modified” is only half an answer. Grosfort shows you the other half: the official original on the left, your file on the right, every difference marked.
The same view compares any file with its own earlier versions from the file watcher.
Login
Failed sign-ins lock an address out, longer each time.
Authenticator apps, e-mail codes and backup codes, required for the roles you choose.
Move the login page to an address only you know.
A password that appears in a known data breach is refused when someone tries to set it.
Error messages do not reveal whether a user name exists, and user names cannot be listed.
Limit or switch off the side doors most sites never use.
Hardening and headers
HSTS, frame protection, referrer and permissions policies, set correctly from the first minute.
Build a policy with presets for the services you use, test it in report-only mode, read the reports in wp-admin.
Hardened cookies and an HTTPS redirect.
Files in the uploads folder cannot run as programs.
Who signed in, what was installed and which settings changed, kept for 30 days or up to a year.
E-mail, Slack, Discord, Google Chat, Mattermost, Rocket.Chat, Telegram, ntfy, Pushover or any webhook.
Coverage
The attacks WordPress sites actually face, and what Grosfort does about each.
| # | Attack | What stops it |
|---|---|---|
| 1 | Brute-force login | Lockouts, a private login address, two-factor sign-in |
| 2 | Credential stuffing | Leaked-password check, two-factor sign-in, the Threat Network |
| 3 | XML-RPC abuse | XML-RPC limited or switched off, pingbacks disabled |
| 4 | Known plugin and theme vulnerabilities | Daily vulnerability check and the firewall |
| 5 | SQL injection | Request inspection |
| 6 | Cross-site scripting | Request inspection and Content Security Policy |
| 7 | Forged admin requests | Requests sent from other websites are refused |
| 8 | Malicious file upload | Upload inspection, and no code can run in uploads |
| 9 | File inclusion and path traversal | Request inspection |
| 10 | Remote code execution and object injection | Request inspection |
| 11 | Privilege escalation | Only an administrator can create an administrator |
| 12 | Settings takeover | Site address, default role and registration are guarded |
| 13 | User enumeration | Blocked on every known route |
| 14 | Backdoors and web shells | Scanner, file watcher, analysis engine, quarantine |
| 15 | Spam links injected into pages | Page scan as visitor and as search engine |
| 16 | Malicious redirects and cloaking | Visitor and search-engine views compared |
| 17 | Tampered or pirated plugins | Checksums against the official packages |
| 18 | Floods and bad bots | Traffic control and attack-tool blocking |
| 19 | Stolen session cookies | Hardened cookies, and a session ends when it changes browser |
| 20 | Exposed backups, logs and folders | Probe blocking and the exposed-file scan |
One site free for the first 1,000 customers. One per organisation. No card required.