Arch Linux Security Advisory ASA-202011-3 ========================================= Severity: Critical Date : 2020-11-03 CVE-ID : CVE-2020-28032 CVE-2020-28033 CVE-2020-28034 CVE-2020-28035 CVE-2020-28036 CVE-2020-28037 CVE-2020-28038 CVE-2020-28039 CVE-2020-28040 Package : wordpress Type : multiple issues Remote : Yes Link : https://security.archlinux.org/AVG-1257 Summary ======= The package wordpress before version 5.5.3-1 is vulnerable to multiple issues including arbitrary code execution, cross-site request forgery, cross-site scripting, insufficient validation and privilege escalation. Resolution ========== Upgrade to 5.5.3-1. # pacman -Syu "wordpress>=5.5.3-1" The problems have been fixed upstream in version 5.5.3. Workaround ========== None. Description =========== - CVE-2020-28032 (arbitrary code execution) WordPress before 5.5.2 mishandles deserialization requests in wp- includes/Requests/Utility/FilteredIterator.php. - CVE-2020-28033 (insufficient validation) WordPress before 5.5.2 mishandles embeds from disabled sites on a multisite network, as demonstrated by allowing a spam embed. - CVE-2020-28034 (cross-site scripting) WordPress before 5.5.2 allows XSS associated with global variables. - CVE-2020-28035 (privilege escalation) WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC. - CVE-2020-28036 (privilege escalation) wp-includes/class-wp-xmlrpc-server.php in WordPress before 5.5.2 allows attackers to gain privileges by using XML-RPC to comment on a post. - CVE-2020-28037 (arbitrary code execution) 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). - CVE-2020-28038 (cross-site scripting) WordPress before 5.5.2 allows stored XSS via post slugs. - CVE-2020-28039 (insufficient validation) is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected. - CVE-2020-28040 (cross-site request forgery) WordPress before 5.5.2 allows CSRF attacks that change a theme's background image. Impact ====== A remote attacker can bypass security restrictions to post spam, spoof content, escalate privileges and execute arbitrary code. References ========== https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-... https://github.com/WordPress/wordpress-develop/commit/add6bedf3a53b647d0ebda... https://github.com/WordPress/wordpress-develop/commit/e2142c20be3c07f7e59310... https://github.com/WordPress/wordpress-develop/commit/2d677cd4b2e24d0b5f17a3... https://github.com/WordPress/wordpress-develop/commit/c9e6b98968025b16290159... https://github.com/WordPress/wordpress-develop/commit/2ca15d1e5ce70493c5c0c0... https://github.com/WordPress/wordpress-develop/commit/d5ddd6d4be1bc9fd16b779... https://blog.wpscan.com/2020/10/30/wordpress-5.5.2-security-release.html https://github.com/WordPress/wordpress-develop/commit/69e832398254b7f47d137a... https://security.archlinux.org/CVE-2020-28032 https://security.archlinux.org/CVE-2020-28033 https://security.archlinux.org/CVE-2020-28034 https://security.archlinux.org/CVE-2020-28035 https://security.archlinux.org/CVE-2020-28036 https://security.archlinux.org/CVE-2020-28037 https://security.archlinux.org/CVE-2020-28038 https://security.archlinux.org/CVE-2020-28039 https://security.archlinux.org/CVE-2020-28040