CVE-2020-28037: WordPress vulnerability

is_blog_installed in wp-includes/functions.php in WordPress before 5.5.2 improperly determines whether WordPress is already installed, which might allow an attacker to perform a new installation, leading to remote code execution (as well as a denial of service for the old installation).

How to mitigate CVE-2020-28037

Time needed: 5 minutes.

Follow the instructions, as they will assist you in mitigating the WordPress vulnerability that been reported in CVE-2020-28037.

  1. Install the latest version of WordPress

    Navigate to the official WordPress website and download the latest version of WordPress. The latest version contains the CVE-2020-28037 fix.
    Update to the latest version

  2. Perform a vulnerability assessment

    Perform a scan on your WordPress environment(s), and check for vulnerabilities. Verify if CVE-2020-28037 has been mitigated.

  3. Utilize the references

    The CVE-2020-28037 references have been provided for a reason. Utilize these references and make sure that you are correctly informed.

References

  • www.debian.org/security/2020/dsa-4784
  • github.com/WordPress/wordpress-develop/commit/2ca15d1e5ce70493c5c0c096ca0c76503d6da07c
  • wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/
  • wpscan.com/vulnerability/10450
  • lists.debian.org/debian-lts-announce/2020/11/msg00004.html
  • Share this information