wpscan VS pfSense

Or you could just run WPScan, a simple open source CLI Wordpress pen testing tool which will scan for 30k+ known WP vulnerabilities. It certainly isn't as comprehensive as hiring a Red Team to attack the site but it can provide baseline assurance that no gaping holes exist in your security config, This should be part of your security hardening workflow if is isnt already.

source: https://wpscan.com/wordpress-security-scanner

Finally, you can use a service like WPScan to fix WordPress issues by scanning your website for plugins and themes that have known security vulnerabilities.

WP is fun but likely has to be running older versions to exploit it, check out and run WPScan against it, https://github.com/wpscanteam/wpscan

You could also run your own scan. There are tools for it. For example, https://github.com/wpscanteam/wpscan

After our initial port scan, we might do more scans depending on what we find. In order to be as effective as possible, and to gather as much information as possible, pentesters are often running multiple scans simultaneously on a target. There are hundreds of tools out there for every service imaginable. Some of the tools worth mentioning are wpscan (https://wpscan.com/wordpress-security-scanner) for Wordpress sites or sqlmap (https://sqlmap.org/) for automatic SQL injection. For a more extensive list of tools check out https://0xcybery.github.io/ehtk/ or https://github.com/enaqx/awesome-pentest

So the website is using Wordpress. Having said that, we are going to use WPScan. But before that, make sure that you have already acquired your API token before using WPScan or you will never be able to utilize the scanner. You can get your own API token by signing up on their website.

One option is Firewalla Gold Plus, or you could buy a mini PC like it and run pfSense/OPNsense yourself.

Download and install pfsense as a virtual machine or partition: https://www.pfsense.org Configure it with the rules you want: https://youtu.be/VAGFGppSt74 Play with it, but be careful because it will block all traffic unless you check everything properly.

Another option is Firewalla, or buy a mini PC like it and run pfSense/OPNsense yourself. Two similar concepts, with the cost being either money or your DIY time. A lot of Firewalla users say that it's much easier for home use than pfSense/OPNsense, so you might find it worthwhile to spend a little more on it upfront and have to tinker less.

If you want firewall, I think you can use https://www.pfsense.org/ or https://opnsense.org/ , maybe running on an old PC or a Raspberry Pi. Not sure.

I've recently started using OPNsense. It's similar to pfSense, but seems to be considered a little more user-friendly.

For most router issues, I recommend people always put them in to dumb bridge mode and put a proper firewall like pfsense or opnsense as your gateway.

I have found that my historical average packet loss is about 0.02%. Something distinctly changed around 4/20 of this year, and now the average packet loss has gone up to 0.05% with spikes even higher, associated with periods of elevated ping times. It rarely did that before. Typically the IPv6 stack has more problems than v4 (especially an incident of packet loss on 4/28), and neither has been trouble-free since I started service in early 2020. My data comes from a pfSense installation.

I have done this using the Pfsense