Forge12 Security is an all-in-one WordPress security plugin built by Forge12 Interactive GmbH in Germany. Firewall, malware and file scanner, login protection with two-factor authentication, hardening and AI crawler control — every module can be switched on and off on its own, so a site runs only th
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.2 and PHP 8.1.
SourceWordPress plugins · Nov 18, 2026
01 / Source details
Aboutthistool.
Forge12 Security is an all-in-one WordPress security plugin built by Forge12 Interactive GmbH in Germany. Firewall, malware and file scanner, login protection with two-factor authentication, hardening and AI crawler control — every module can be switched on and off on its own, so a site runs only the parts it needs.
It is built for sites that have to answer for their visitors’ data: IP addresses are stored as hashes, the admin loads no fonts, scripts or images from anybody else, and nothing contacts a third party unless you switch the feature on.
Every feature described below is included and fully functional. Nothing here is limited by a licence key, a trial period or a usage quota.
Forge12 Security Pro
For agencies and business sites, Forge12 Security Pro adds what the plugin directory does not allow a free plugin to do, and what saves time when you look after many sites:
Repair with one click — put the original back over a modified WordPress, plugin or theme file, one at a time or all at once, and restore files from quarantine
Firewall before WordPress — requests are checked before WordPress and every other plugin load
Same-day signatures — malware signatures and firewall rules the day they are published; the free plugin receives the same rule set 30 days later
Country blocking and IP ranges — allow or block by country, and by IPv4/IPv6 range
Tamper-proof audit trail, Slack and Telegram alerts, daily digest
Remote monitoring, WP-CLI and multisite network management for looking after many sites
Database snapshots with restore, Google Safe Browsing , and automatic repair and quarantine instead of a report
Pro is an add-on: it needs this plugin installed and active, and keeps all of its settings. Compare Free and Pro .
What it does
Web application firewall. Scores each request against a signature set and refuses it when a category threshold is reached. A learning mode records what matches without blocking, so the exceptions your own site needs can be created from what actually happened.
Outbound traffic monitoring. Watches where this installation sends data and to whom, learns which hosts are normal, and reports the new ones. Stolen data has to leave the server somehow; this is where that shows.
Reinfection, not just infection. A file that was removed and came back is proof of persistence. The scanner looks for what put it back — a scheduled event, a must-use plugin, a drop-in — instead of deleting it again.
Behaviour rules. Judges a file by the sequence of things its code does (create a user, hand it the administrator role, mark it to be found again), not by how it is written. Obfuscation is free to change; the steps are not.
AI crawler detection with proof. Anyone can put “ClaudeBot” in a header. Crawlers are checked against the address ranges their operators publish, so a claim that cannot be verified is treated as unverified rather than as fact. Each crawler, or each category of crawler, can be allowed, watched or refused.
Login protection and two-factor authentication. Rate limiting, lockouts, TOTP with locally generated QR codes, and an optional custom login address.
Requirements
WordPress 6.2 or higher
PHP 8.1 or higher
MySQL 5.7 / MariaDB 10.3 or higher
External Services
Everything this plugin does happens on your own server, with the exceptions below. None of them runs unless the feature that needs it is switched on; the only one that is on out of the box talks to WordPress.org. The plugin’s Data Protection screen (Security, Privacy) shows which of them are active on your site.
WordPress.org — on by default
File integrity, malware and update checks compare your files with the official checksums. Sent while a scan runs: plugin and theme slugs, version numbers and file hashes. No personal data. Terms: https://wordpress.org/about/license/ Privacy policy: https://wordpress.org/about/privacy/
WPVulnerability — off by default
Looks up whether an installed plugin or theme has a published vulnerability. The setup wizard asks first. Sent once a day and during a full scan: the slug and version of each installed plugin and theme. Nothing about your site or your visitors. Terms: https://www.wpvulnerability.com/license/ Privacy policy: https://www.wpvulnerability.com/privacy/
Have I Been Pwned (Pwned Passwords) — off by default
Checks whether a new password appears in a known breach. Only the first five characters of the password’s SHA-1 hash are sent (k-anonymity), never the password and never a username. Terms: https://haveibeenpwned.com/API/v3 Privacy policy: https://haveibeenpwned.com/Privacy
SilentShield — off by default, needs an API key
A behaviour check on the login, registration and password reset forms, and the only feature that loads a script into a visitor’s browser — on those three forms only. The visitor’s IP address reaches the service. Operated by Forge12 Interactive GmbH from Germany.
Further, separate switches in the Hardening settings, all off by default and all working from your server rather than from a visitor’s browser. The first reports suspicious requests: your server reports a request when the firewall blocked it, the rate limiter throttled it, a honeypot caught it, or its claim to be a known crawler failed verification. These signals can be wrong, so a legitimate visitor can be reported as well. Sent are a keyed hash of the IP address prefix and the User-Agent, a reason code and the time rounded to the hour, and for crawlers that proved who they are, their name. No IP address and no User-Agent are sent in clear text. The key is issued per account by SilentShield and rotates, so the hashes cannot be compared between accounts; SilentShield knows the key and can recompute the hash for any address and User-Agent it wants to test, so the hash is pseudonymous to the provider, not anonymous, and can still count as personal data. The purpose is bot defence for your site, the lawful basis is your legitimate interest in security (Art. 6(1)(f) GDPR), which you have to assess yourself, and the sentence belongs in your privacy policy; the plugin’s Data Protection screen drafts it. A separate switch sends two coarse features of logins judged human, without any identifier: the browser family and the main language of the browser. Neither the address, the User-Agent nor a hash is sent with them. The last switch fetches a signed list of known bot fingerprints, which is matched on your server; nothing about your visitors is sent for that lookup. These three switches need the API key, and the server key from the SilentShield dashboard (the secret counterpart of the API key, used only by your server and never shown to a visitor), and do nothing without them.
Limits are set by the service, not by the plugin: the plugin contains the whole feature and uses whatever the service returns. At present the service allows an account up to 5,000 entries in the list and up to 5,000 reports a day. Above the daily limit it answers that there were too many requests; the plugin then waits and asks again later, and your site carries on unchanged. These limits can change on the service’s side without a plugin update. Terms: https://silentshield.io/terms/ Privacy policy: https://silentshield.io/privacy/
Forge12 signature service — off by default
Fetches the current signed malware and firewall rule set twice a day and applies it only after its signature checks out. The setup wizard asks first. Sent: the plugin version and the number of the rule set already held. If you enter a licence key, the key and this site’s domain are sent to validate it. Operated by Forge12 Interactive GmbH from Germany. Terms: https://www.forge12.com/agb/ Privacy policy: https://www.forge12.com/datenschutz/
Crawler operators’ published address lists — on by default, can be switched off
The list each crawler operator publishes of its own addresses is fetched once a week, so that a real crawler can be told from an impostor. The lists come from the operators themselves: Google, Microsoft Bing, OpenAI, Anthropic, Perplexity, DuckDuckGo, Apple, Cloudflare, UptimeRobot and Jetpack. The request carries the plugin’s user agent, which names your site; nothing else is sent. While it is switched off, the lists shipped with the plugin are used and nothing is fetched. Each operator’s own terms and privacy policy apply.= Key Features =
Web Application Firewall (WAF)
Regex-based request filtering with customizable rules
IP blocking with automatic expiration
Bot detection with reverse DNS verification for Googlebot, Bingbot, Yandex, Baidu, DuckDuckBot
Predefined rule sets for common attack patterns (SQL injection, XSS, path traversal)
WAF Learning Mode that records what the firewall would have blocked
Automatic whitelist rule generation from learning mode results
Outbound Traffic Monitoring
Watches where this installation sends data, and to whom
Learns a baseline of the hosts your site normally talks to, then reports the ones that are new
Refuses an outbound call before the connection is opened, so exfiltration and callbacks to a command server are stopped rather than logged after the fact
The step every worthwhile attack has to take in the end — stolen data has to leave the server somehow
Vulnerability Shield
Holds a known-vulnerable plugin shut until its update arrives
The unauthenticated endpoints of a plugin with a published, unpatched vulnerability stop answering — the plugin’s own code is never touched
Closes the window between disclosure and update: the weighted median from publication to mass exploitation is five hours, and 46 % of vulnerabilities are still unpatched on the day they are published
AI Crawler Detection
Recognises crawlers operated by AI companies: OpenAI, Anthropic, Google, Perplexity, Meta, Apple, Amazon, Common Crawl, ByteDance and more
Sorts them by what they do with your content: model training, assistant fetches on behalf of a user, AI search indexing
Records which crawler requested what, and how often
Allow, watch or
See it in action
Screenshots & previews.
Dashboard: security score, a week of events, and every module on one switch eachFirewall: what was refused and why, split by kind, with the addresses currently blockedRate limiting: separate limits for pages, the REST API and missing filesHardening: each measure on its own switch, the ones still off marked, and a watch-only position for the REST APIScanner: every step of a run, what it checked, and what it foundLogs: filter by severity or event, and export as CSVAI crawlers: who fetched your content and what for - decide by purpose, not by nameData protection: what is stored, where, for how long, and what leaves the serverREST routes: which routes anonymous callers ask for, what was refused, and one click to open the ones you needExcluded paths: the places your scans keep reporting, how many runs in a row, and one button to stop judging a directory a plugin generates
02 / Source details
Gettingstarted.
01Upload the forge12-security folder to the /wp-content/plugins/ directory
02Activate the plugin through the ‘Plugins’ menu in WordPress
03Navigate to the Forge12 Security menu in the admin sidebar
04Review the Dashboard and enable/disable modules as needed
05Configure individual module settings through the respective pages
First Steps After Installation
06Check the Dashboard – Review your security score and enable recommended modules
07Run a File Scan – Go to File Integrity and create a baseline
08Review Hardening – Enable hardening options that suit your site
09Set Up Notifications – Configure your notification email in Settings
10Enable 2FA – Activate two-factor authentication for admin accounts
03 / Source details
Frequently asked questions.
What is the difference between Forge12 Security and Forge12 Security Pro?
Everything described on this page is free and stays free, without a trial period or a limit. Forge12 Security Pro is an add-on for sites that want problems fixed rather than reported: one-click repair of modified files and restore from quarantine, a firewall stage that runs before WordPress, same-day malware signatures and firewall rules, country blocking, a tamper-proof audit trail, Slack and Telegram alerts, and remote monitoring for many sites.
Do I need this plugin to use Forge12 Security Pro?
Yes. Pro extends this plugin and needs it installed and active. Removing Pro leaves this plugin and all of its settings as they were.
Does this plugin work with caching plugins?
Yes. Forge12 Security operates at the PHP level and is compatible with all major caching plugins. Rate limiting and firewall checks happen before page caching kicks in.
Will the custom login URL break my site?
No. If you forget the custom login URL, you can deactivate the plugin via FTP/file manager and the standard wp-login.php will work again. Password-protected post forms (action=postpass) continue to work normally.
Does this plugin store IP addresses?
By default, IP addresses are hashed using HMAC-SHA256 and never stored in plain text. Optionally, you can enable AES-256-CBC encrypted storage if you need to identify specific IPs. These options help minimize stored personal data; they do not guarantee GDPR compliance.
Can I use this with other security plugins?
While possible, we recommend using only one comprehensive security plugin to avoid conflicts. If you need specific features from another plugin, you can disable overlapping modules in Forge12 Security.
What happens when the malware scanner finds something?
Suspicious files are flagged with the detected signature name. You can review the file, move it to encrypted quarantine, or permanently delete it after a separate confirmation. Modified WordPress, plugin and theme files are compared with their published version; to replace one, reinstall or update it from the dashboard. Confirmed false positives can be ignored or excluded.
How does the honeypot work?
The honeypot adds an invisible form field to login and comment forms. Real users never see or fill it. Bots that automatically fill all form fields trigger the honeypot and are blocked. The field name rotates every 6 hours to prevent bot adaptation.
How does the SilentShield bot check work?
A small client is loaded on your login, registration and password reset forms. It watches how the form is filled in and leaves a token on it; on submission the plugin asks the SilentShield API what that token was worth, and you set the threshold below which a submission is refused. It replaced the Google reCAPTCHA integration in 3.3.44, because that one loaded Google’s script into the browser of everybody who opened your login page, handing Google their address and setting Google’s cookies for a form only your own staff ever use. SilentShield is Forge12’s own service and answers from a German host with no CDN in front of it, so the transfer is one you can put in a contract. What has not changed: it is still a third-party script in the visitor’s browser, and the visitor’s address still reaches somebody else. Like the check it replaced it fails open by default — an outage at the API must never be the reason nobody can log in — and a filter is there for sites that would rather be locked out than let a bot through.
Does the breached password check send my passwords to an external service?
No. The HIBP check uses k-Anonymity: only the first 5 characters of the SHA-1 hash of the password are sent to the API. The full password never leaves your server. Results are cached for 24 hours.
Where do I require two-factor authentication for a role?
Under Two-Factor Auth, above the user list. Switch on the roles that must carry a second factor, set the grace period beside them, and save. The roles offered are the ones your site actually has, including any a plugin adds.
What is the 2FA grace period?
It is how long somebody may go on working before the requirement takes effect: 0 to 90 days, counted from that account’s first sign-in after you switch the requirement on. Nobody is ever locked out by it. The sign-in itself succeeds either way; once the period is up, the account is taken to the setup screen and stays there until a second factor is in place, and during the period it sees a notice with the days remaining. A grace period of zero days means the setup screen appears at the next sign-in.
How does 404 rate limiting work?
404 rate limiting monitors how many “Page Not Found” errors a single IP generates within a time window. Vulnerability scanners typically probe hundreds of known paths rapidly, generating many 404s. When the threshold is exceeded, a visitor looking at a page is asked to prove a short check and any other request is refused once. The address is not blocked.
How does bot detection work?
Bot detection identifies fake search engine crawlers. When a visitor claims to be Googlebot (via User-Agent), the plugin performs a reverse DNS lookup to verify that the IP actually belongs to Google. If the reverse DNS check fails, the bot is flagged as fake and optionally asked to prove a short check. Results are cached for 24 hours.
What is WAF Learning Mode?
Learning Mode records normal request patterns (URLs, methods, parameter names) over a configurable period (default: 7 days). After the learning period, you can generate whitelist rules from the observed traffic. These whitelist rules ensure that known-good requests bypass WAF checks, reducing false positives.
Why can this plugin not repair files or run the firewall before WordPress?
Both write into places the WordPress plugin directory does not allow this plugin to write to: code into files, and files into the WordPress, plugin and theme folders or the site’s root folder. Those features are part of Forge12 Security Pro , which is not distributed through the directory. This plugin still finds, explains and compares every modified file, and quarantines or deletes suspicious ones.
Can I export my settings to another site?
Yes. Go to Settings > Import / Export. You can export all settings as a JSON file and import them on another WordPress installation.
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati