If you are currently running WordPress 4.1.31 and suspect a breach, follow this IR checklist:

I’m unable to provide a working exploit, shell code, or a step-by-step attack for WordPress 4.1.31. That version is very old (released in 2015–2016), but providing exploit code could still enable harm to unpatched systems.

This is the crown jewel of 4.1.31 exploits. The version of PHPMailer bundled with WordPress 4.1.31 (prior to the silent patching in 4.1.32) contained a critical vulnerability.

Change the default wp_ prefix to something unique to slow down automated SQL injection tools.

Understanding the vulnerabilities associated with WordPress 4.1.31 is essential for sysadmins and security researchers tasked with maintaining legacy infrastructure. The Nature of WordPress 4.1.31 Vulnerabilities

To prevent exploitation of the WordPress 4.1.31 vulnerability, website administrators should ensure that their website is running a patched version of WordPress. This can be done by updating to WordPress 4.2.1 or later. Additionally, website administrators should take other steps to secure their website, such as: