Critical Remote Code Execution Vulnerability in WordPress - CVE-2020-28037
Summary
CVE-2020-28037: 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 e... Affects wordpress across 3 version ranges.
< 2ca15d1e5ce70493c5c0c096ca0c76503d6da07c
< 5.5.3+dfsg1-1
< e86313b568fbd86fcd8e743a59be939d627c7e0d
Fixed in 5.5.3+dfsg1-1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
WordPress is a widely-used open-source content management system (CMS) that enables users to create and manage websites easily. It offers a rich ecosystem of plugins and themes, making it highly customizable. However, like any software, WordPress is susceptible to vulnerabilities. CVE-2020-28037 is a significant security flaw that affects WordPress installations prior to version 5.5.2, allowing unauthorized installations and potential remote code execution.
Vulnerability Detail
The vulnerability arises from the function is_blog_installed in wp-includes/functions.php, which fails to accurately determine if WordPress is already installed. This flaw can be exploited by attackers to initiate a new installation of WordPress, potentially leading to remote code execution. The ramifications include unauthorized access to the server, data breaches, and denial of service for existing installations. The CVSS score for this vulnerability is 9.8, indicating its critical severity.
How To Fix
Minimum fixed version
5.5.3+dfsg1-1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade wordpressTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate upgrading is not feasible, consider disabling the installation feature temporarily by restricting access to the wp-admin directory or implementing firewall rules to block unauthorized access. However, this is not a permanent solution and upgrading is strongly recommended.
Conclusion
CVE-2020-28037 is a critical vulnerability that poses significant risks to WordPress installations prior to version 5.5.2. It is essential for users to upgrade to the latest version to mitigate these risks and protect their websites from potential attacks.
See every vulnerability recorded for wordpress →
FAQ
CVE-2020-28037 is a critical vulnerability in WordPress that allows attackers to perform unauthorized installations, potentially leading to remote code execution.
You can check if your WordPress site is affected by using tools like Vulert, which monitors open-source vulnerabilities in your software.
If you cannot upgrade immediately, implement temporary workarounds such as restricting access to the wp-admin directory.
Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential downtime for your website.
More information can be found on the official CVE website and through security advisories related to WordPress.
Related vulnerabilities
Recent vulnerabilities recorded for wordpress.
