jaimenj

<p>A very simple firewall for WordPress that allows you to see all real requests to your WordPress and protect you from Internet attacks. It’s a WAF, a Web Application Firewall that is installed in front of WordPress. It’s installed in the server with the plugin, and it checks requests from the web browsers, bots or webcrawlers to your WordPress. It executes the WAF codes before every request to PHP files of WordPress, so it also works before every request to the WordPress cache.</p>
<p>Features:</p>
<ul>
<li>Feel free to contribute in GitHub to improve the project.</li>
<li>It’s free, completely free.</li>
<li>Detection and protection of DoS attacks.</li>
<li>Detection and notification of possible DDoS attacks.</li>
<li>It can protect you against SQL injection, XSS and Xploit attacks using your own Regexes.</li>
<li>Permanent block or bypass of custom IPs, it allows you to configure IPs with your own Regexes too.</li>
<li>Log and show Regex errors, for debug and improve your Regexes.</li>
<li>Save payloads, all or only when match a regex.</li>
<li>Block and allow countries and continents.</li>
<li>404s detections.</li>
<li>Show URLs or IPs doing 404s.</li>
<li>Show IPs that are doing most of the visits.</li>
<li>Show URLs most visited.</li>
</ul>
<h3>Uninstall</h3>
<ol>
<li>Uninstall .user.ini file.</li>
<li>Deactivate the plugin into the Plugins menu in the admin panel of WordPress.</li>
<li>Delete into the Plugins menu.</li>
</ol>
<p>All the options configured into the plugin are removed when plugin is deleted, not when plugin is deactivated. All the database tables are removed when plugin is deactivated. So if you want to remove the plugin and all data stored, first deactivate the plugin and then remove it from the plugin admin zone into the WordPress backend.</p>


What's going on

A simple Web Application Firewall for WordPress.

Maikuolan

<p>CIDRAM (Classless Inter-Domain Routing Access Manager) is a PHP script designed to protect websites by blocking requests originating from IP addresses regarded as being sources of undesirable traffic, including (but not limited to) traffic from non-human access endpoints, cloud services, spambots, scrapers, etc. It does this by calculating the possible CIDRs of the IP addresses supplied from inbound requests and then attempting to match these possible CIDRs against its signature files (these signature files contain lists of CIDRs of IP addresses regarded as being sources of undesirable traffic); If matches are found, the requests are blocked.</p>
<h3>Requirements</h3>
<ul>
<li>PHP >= 7.2.0</li>
<li>PCRE</li>
</ul>
<h3>Updating</h3>
<p>Note: CIDRAM does not interact in any way with your database, and stores its own configuration settings, customisations, and related materials as flatfiles within its own directory. If you’ve not changed any of the default configuration settings and if you’re not using any customisations for this plugin, updating normally via the plugins dashboard, without need for any additional steps, should be sufficient and shouldn’t cause any problems. However, if you’ve modified the configuration settings for CIDRAM, or if you’ve made any customisations, I would recommend making backups of all of these prior to updating, due to that updating will overwrite all settings and customisations (after updating, you can then restore your customisations from your backups). Alternatively, if you update via the CIDRAM front-end updates page, all settings and customisations should be preserved.</p>


CIDRAM

CIDRAM: A PHP-level CIDR/IP-based firewall solution.

What's going on vs CIDRAM