Bitnami package
wordpress
pkg:bitnami/wordpress
Vulnerabilities (63)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-29450 | — | >= 4.7.0, < 5.7.1 | 5.7.1 | Apr 15, 2021 | 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-29447 | — | >= 5.6.0, < 5.7.1 | 5.7.1 | Apr 15, 2021 | 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-28032 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php. | ||
| CVE-2020-28033 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 mishandles embeds from disabled sites on a multisite network, as demonstrated by allowing a spam embed. | ||
| CVE-2020-28034 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 allows XSS associated with global variables. | ||
| CVE-2020-28036 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | 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 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | 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-28038 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 allows stored XSS via post slugs. | ||
| CVE-2020-28040 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 allows CSRF attacks that change a theme's background image. | ||
| CVE-2020-28039 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | 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-28035 | — | < 5.5.2 | 5.5.2 | Oct 31, 2020 | WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC. | ||
| CVE-2020-25286 | — | < 5.4.2 | 5.4.2 | Sep 13, 2020 | 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-4047 | — | >= 3.7.0, < 3.7.34 | 3.7.34 | Jun 12, 2020 | 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 | ||
| CVE-2020-4048 | — | >= 3.7.0, < 3.7.34 | 3.7.34 | Jun 12, 2020 | 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-4049 | — | >= 3.7.0, < 3.7.34 | 3.7.34 | Jun 12, 2020 | 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-4050 | — | >= 3.7.0, < 3.7.34 | 3.7.34 | Jun 12, 2020 | 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-4046 | — | >= 3.7.0, < 3.7.34 | 3.7.34 | Jun 12, 2020 | In affected versions of WordPress, users with low privileges (like contributors and authors) can use the embed block in a certain way to inject unfiltered HTML in the block editor. When affected posts are viewed by a higher privileged user, this could lead to script execution in | ||
| CVE-2020-11026 | — | >= 3.7.0, < 3.7.33 | 3.7.33 | Apr 30, 2020 | In affected versions of WordPress, files with a specially crafted name when uploaded to the Media section can lead to script execution upon accessing the file. This requires an authenticated user with privileges to upload files. This has been patched in version 5.4.1, along with | ||
| CVE-2020-11028 | — | < 5.4.1 | 5.4.1 | Apr 30, 2020 | In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5. | ||
| CVE-2020-11029 | — | >= 3.7.0, < 3.7.33 | 3.7.33 | Apr 30, 2020 | In affected versions of WordPress, a vulnerability in the stats() method of class-wp-object-cache.php can be exploited to execute cross-site scripting (XSS) attacks. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3 |
- CVE-2021-29450Apr 15, 2021affected >= 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-29447Apr 15, 2021affected >= 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-28032Oct 31, 2020affected < 5.5.2fixed 5.5.2
WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.
- CVE-2020-28033Oct 31, 2020affected < 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-28034Oct 31, 2020affected < 5.5.2fixed 5.5.2
WordPress before 5.5.2 allows XSS associated with global variables.
- CVE-2020-28036Oct 31, 2020affected < 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-28037Oct 31, 2020affected < 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-28038Oct 31, 2020affected < 5.5.2fixed 5.5.2
WordPress before 5.5.2 allows stored XSS via post slugs.
- CVE-2020-28040Oct 31, 2020affected < 5.5.2fixed 5.5.2
WordPress before 5.5.2 allows CSRF attacks that change a theme's background image.
- CVE-2020-28039Oct 31, 2020affected < 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-28035Oct 31, 2020affected < 5.5.2fixed 5.5.2
WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC.
- CVE-2020-25286Sep 13, 2020affected < 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-4047Jun 12, 2020affected >= 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
- CVE-2020-4048Jun 12, 2020affected >= 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-4049Jun 12, 2020affected >= 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-4050Jun 12, 2020affected >= 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-4046Jun 12, 2020affected >= 3.7.0, < 3.7.34fixed 3.7.34
In affected versions of WordPress, users with low privileges (like contributors and authors) can use the embed block in a certain way to inject unfiltered HTML in the block editor. When affected posts are viewed by a higher privileged user, this could lead to script execution in
- CVE-2020-11026Apr 30, 2020affected >= 3.7.0, < 3.7.33fixed 3.7.33
In affected versions of WordPress, files with a specially crafted name when uploaded to the Media section can lead to script execution upon accessing the file. This requires an authenticated user with privileges to upload files. This has been patched in version 5.4.1, along with
- CVE-2020-11028Apr 30, 2020affected < 5.4.1fixed 5.4.1
In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.
- CVE-2020-11029Apr 30, 2020affected >= 3.7.0, < 3.7.33fixed 3.7.33
In affected versions of WordPress, a vulnerability in the stats() method of class-wp-object-cache.php can be exploited to execute cross-site scripting (XSS) attacks. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3
Page 3 of 4