wpscan VS CVE-2021-3560-Polkit-Privilege-Esclation

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.

@secnigma has actually written a PoC (proof-of-concept) for this. Let's copy the contents, and paste it on the server using vim.