wordpress-multisite

Vulnerabilities (67)

• CVE-2021-39202HigSep 9, 2021
  affected >= 5.8-beta1.0, <= 5.8-beta1.0

  WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions the widgets editor introduced in WordPress 5.8 beta 1 has improper handling of HTML input in the Custom HTML feature. This leads to store

• CVE-2021-39201HigSep 9, 2021
  affected >= 5.0.0, < 5.8.0fixed 5.8.0

  WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. ### Impact The issue allows an authenticated but low-privileged user (like contributor/author) to execute XSS in the editor. This bypasses the restrictions im

• CVE-2021-39200MedSep 9, 2021
  affected >= 5.2.0, < 5.8.1fixed 5.8.1

  WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. In affected versions output data of the function wp_die() can be leaked under certain conditions, which can include data like nonces. It can then be used to p

• CVE-2020-36326CriApr 28, 2021
  affected >= 3.7.0, < 3.7.36fixed 3.7.36

  PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHP

• CVE-2021-29450MedApr 15, 2021
  affected >= 4.7.0, < 5.7.1fixed 5.7.1

  Wordpress is an open source CMS. One of the blocks in the WordPress editor can be exploited in a way that exposes password-protected posts and pages. This requires at least contributor privileges. This has been patched in WordPress 5.7.1, along with the older affected versions vi

• CVE-2021-29447HigApr 15, 2021
  affected >= 5.6.0, < 5.7.1fixed 5.7.1

  Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks. This requires WordPress installation to be using PHP 8. Access to internal files is possible in a successful XXE

• CVE-2020-28040MedNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 allows CSRF attacks that change a theme's background image.

• CVE-2020-28039CriNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  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-28038MedNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 allows stored XSS via post slugs.

• CVE-2020-28037CriNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  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 install

• CVE-2020-28036CriNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  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-28035CriNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC.

• CVE-2020-28034MedNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 allows XSS associated with global variables.

• CVE-2020-28033HigNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 mishandles embeds from disabled sites on a multisite network, as demonstrated by allowing a spam embed.

• CVE-2020-28032CriNov 2, 2020
  affected < 5.5.2fixed 5.5.2

  WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.

• CVE-2020-25286MedSep 13, 2020
  affected < 5.4.2fixed 5.4.2

  In wp-includes/comment-template.php in WordPress before 5.4.2, comments from a post or page could sometimes be seen in the latest comments even if the post or page was not public.

• CVE-2020-4050LowJun 12, 2020
  affected >= 3.7.0, < 3.7.34fixed 3.7.34

  In affected versions of WordPress, misuse of the `set-screen-option` filter's return value allows arbitrary user meta fields to be saved. It does require an admin to install a plugin that would misuse the filter. Once installed, it can be leveraged by low privileged users. This h

• CVE-2020-4049LowJun 12, 2020
  affected >= 3.7.0, < 3.7.34fixed 3.7.34

  In affected versions of WordPress, when uploading themes, the name of the theme folder can be crafted in a way that could lead to JavaScript execution in /wp-admin on the themes page. This does require an admin to upload the theme, and is low severity self-XSS. This has been patc

• CVE-2020-4048MedJun 12, 2020
  affected >= 3.7.0, < 3.7.34fixed 3.7.34

  In affected versions of WordPress, due to an issue in wp_validate_redirect() and URL sanitization, an arbitrary external link can be crafted leading to unintended/open redirect when clicked. This has been patched in version 5.4.2, along with all the previously affected versions v

• CVE-2020-4047MedJun 12, 2020
  affected >= 3.7.0, < 3.7.34fixed 3.7.34

  In affected versions of WordPress, authenticated users with upload permissions (like authors) are able to inject JavaScript into some media file attachment pages in a certain way. This can lead to script execution in the context of a higher privileged user when the file is viewed