Répertoire de sécurité WordPress
Vulnérabilités du cœur WordPress, page 6
Consultez 380 vulnérabilités connues du cœur WordPress, avec CVE, gravité CVSS, versions affectées et correctifs disponibles. Page 6 de l’annuaire.
WordPress Core
Failles et CVE du cœur WordPress
WordPress Core < 5.2.3 – Reflected Cross-Site Scripting
WordPress before 5.2.3 allows reflected XSS in the dashboard.
[*, 3.7), 3.7-3.7.29, 3.8-3.8.29, 3.9-3.9.27, 4.0-4.0.26, 4.1-4.1.26, 4.2-4.2.23, 4.3-4.3.19, 4.4-4.4.18, 4.5-4.5.17, 4.6-4.6.13, 4.7-4.7.13, 4.8-4.8.9, 4.9-4.9.10, 5.0-5.0.5, 5.1-5.1.1, 5.2-5.2.2
3.7.30, 3.8.30, 3.9.28, 4.0.27, 4.1.27, 4.2.24, 4.3.20, 4.4.19, 4.5.18, 4.6.15, 4.7.14, 4.8.10, 4.9.11, 5.0.6, 5.1.2, 5.2.3
05/09/2019
WordPress Core < 5.2.3 – Cross-Site Scripting via Media Uploads
WordPress before 5.2.3 allows XSS in media uploads because wp_ajax_upload_attachment is mishandled.
[*, 3.7), 3.7-3.7.29, 3.8-3.8.29, 3.9-3.9.27, 4.0-4.0.26, 4.1-4.1.26, 4.2-4.2.23, 4.3-4.3.19, 4.4-4.4.18, 4.5-4.5.17, 4.6-4.6.13, 4.7-4.7.13, 4.8-4.8.9, 4.9-4.9.10, 5.0-5.0.5, 5.1-5.1.1, 5.2-5.2.2
3.7.30, 3.8.30, 3.9.28, 4.0.27, 4.1.27, 4.2.24, 4.3.20, 4.4.19, 4.5.18, 4.6.15, 4.7.14, 4.8.10, 4.9.11, 5.0.6, 5.1.2, 5.2.3
05/09/2019
WordPress Core < 5.1.1 – Cross-Site Request Forgery to Cross-Site Scripting via Comments
WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed…
[*, 3.7), 3.7-3.7.28, 3.8-3.8.28, 3.9-3.9.26, 4.0-4.0.25, 4.1-4.1.25, 4.2-4.2.22, 4.3-4.3.18, 4.4-4.4.17, 4.5-4.5.16, 4.6-4.6.13, 4.7-4.7.12, 4.8-4.8.8, 4.9-4.9.9, 5.0-5.0.3, 5.1
3.7.29, 3.8.29, 3.9.27, 4.0.26, 4.1.26, 4.2.23, 4.3.19, 4.4.18, 4.5.17, 4.6.14, 4.7.13, 4.8.9, 4.9.10, 5.0.4, 5.1.1
12/04/2019
WordPress Core <= 5.0.3 – Path Traversal and Local File Inclusion
WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as…
*-5.0.2
5.0.3
19/02/2019
WordPress Core < 5.0.1 – Remote Code Execution
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring. An attacker with author privileges can…
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
19/02/2019
WordPress Core < 5.0.1 Reflected Cross-Site Scripting
In WordPress before 4.9.9 and 5.x before 5.0.1, crafted URLs could trigger XSS for certain use cases involving plugins.
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – Sensitive Information Disclosure
In WordPress before 4.9.9 and 5.x before 5.0.1, the user-activation page could be read by a search engine's web crawler if an unusual configuration were chosen. The search engine could then index and display a user's e-mail address…
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – Authorization Bypass
In WordPress before 4.9.9 and 5.x before 5.0.1, authors could bypass intended restrictions on post types via crafted input.
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – Authenticated Stored Cross-Site Scripting via Comments
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could modify new comments made by users with greater privileges, possibly causing XSS.
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – Arbitrary File Deletion
In WordPress before 4.9.9 and 5.x before 5.0.1, authors could modify metadata to bypass intended restrictions on deleting files.
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – Stored Cross-Site Scripting via File Uploads
In WordPress before 4.9.9 and 5.x before 5.0.1, when the Apache HTTP Server is used, authors could upload crafted files that bypass intended MIME type restrictions, leading to XSS, as demonstrated by a .jpg file without JPEG data.
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – PHP Object Injection
In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could conduct PHP object injection attacks via crafted metadata in a wp.getMediaItem XMLRPC call. This is caused by mishandling of serialized data at phar:// URLs in the wp_get_attachment_thumb_file function…
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
12/12/2018
WordPress Core < 5.0.1 – PHAR Unserialization
WordPress Core versions before 5.0.1 contain a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution due to an incomplete fix for CVE-2017-1000600. This attack appears to be exploitable via thumbnail upload by…
[*, 3.7), 3.7-3.7.27, 3.8-3.8.27, 3.9-3.9.25, 4.0-4.0.24, 4.1-4.1.24, 4.2-4.2.21, 4.3-4.3.17, 4.4-4.4.16, 4.5-4.5.15, 4.6-4.6.12, 4.7-4.7.11, 4.8-4.8.7, 4.9-4.9.8, 5.0
3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.1
06/09/2018
WordPress Core < 4.9 – Insecure Deserialization
WordPress version
[*, 4.9)
4.9
16/08/2018
WordPress Core < 6.4.3 – Authenticated(Administrator+) PHP File Upload
In all current versions of WordPress Core before 6.4.3, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin…
[*, 4.1), 4.1-4.1.39, 4.2-4.2.36, 4.3-4.3.32, 4.4-4.4.31, 4.5-4.5.30, 4.6-4.6.27, 4.7-4.7.27, 4.8-4.8.23, 4.9-4.9.24, 5.0-5.0.20, 5.1-5.1.17, 5.2-5.2.19, 5.3-5.3.16, 5.4-5.4.14, 5.5-5.5.13, 5.6-5.6.12, 5.7-5.7.10, 5.8-5.8.8, 5.9-5.9.8, 6.0-6.0.6, 6.1-6.1.4, 6.2-6.2.3, 6.3-6.3.2, 6.4-6.4.2
4.1.40, 4.2.37, 4.3.33, 4.4.32, 4.5.31, 4.6.28, 4.7.28, 4.8.24, 4.9.25, 5.0.21, 5.1.18, 5.2.20, 5.3.17, 5.4.15, 5.5.14, 5.6.13, 5.7.11, 5.8.9, 5.9.9, 6.0.7, 6.1.5, 6.2.4, 6.3.3, 6.4.3
04/08/2018
WordPress Core < 4.9.7 – Authenticated Arbitrary File Deletion
WordPress through 4.9.6 allows Author users to execute arbitrary code by leveraging directory traversal in the wp-admin/post.php thumb parameter, which is passed to the PHP unlink function and can delete the wp-config.php file. This is related to missing…
[*, 3.7), 3.7-3.7.26, 3.8-3.8.26, 3.9-3.9.24, 4.0-4.0.23, 4.1-4.1.23, 4.2-4.2.20, 4.3-4.3.16, 4.4-4.4.15, 4.5-4.5.14, 4.6-4.6.11, 4.7-4.7.10, 4.8-4.8.6, 4.9-4.9.6
3.7.27, 3.8.27, 3.9.25, 4.0.24, 4.1.24, 4.2.21, 4.3.17, 4.4.16, 4.5.15, 4.6.12, 4.7.11, 4.8.7, 4.9.7
05/07/2018
WordPress Core < 4.9.5 – Open Redirect
Before WordPress 4.9.5, the redirection URL for the login page was not validated or sanitized if forced to use HTTPS.
[*, 3.7), 3.7-3.7.25, 3.8-3.8.25, 3.9-3.9.23, 4.0-4.0.22, 4.1-4.1.22, 4.2-4.2.19, 4.3-4.3.15, 4.4-4.4.14, 4.5-4.5.13, 4.6-4.6.10, 4.7-4.7.9, 4.8-4.8.5, 4.9-4.9.4
3.7.26, 3.8.26, 3.9.24, 4.0.23, 4.1.23, 4.2.20, 4.3.16, 4.4.15, 4.5.14, 4.6.11, 4.7.10, 4.8.6, 4.9.5
03/04/2018
WordPress Core < 4.9.5 – Authenticated Stored Cross-Site Scripting via Generator Tag
Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag.
[*, 3.7), 3.7-3.7.25, 3.8-3.8.25, 3.9-3.9.23, 4.0-4.0.22, 4.1-4.1.22, 4.2-4.2.19, 4.3-4.3.15, 4.4-4.4.14, 4.5-4.5.13, 4.6-4.6.10, 4.7-4.7.9, 4.8-4.8.5, 4.9-4.9.4
3.7.26, 3.8.26, 3.9.24, 4.0.23, 4.1.23, 4.2.20, 4.3.16, 4.4.15, 4.5.14, 4.6.11, 4.7.10, 4.8.6, 4.9.5
03/04/2018
WordPress Core < 4.9.5 – Security Misconfiguration with URL Hostnames
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
[*, 3.7), 3.7-3.7.25, 3.8-3.8.25, 3.9-3.9.23, 4.0-4.0.22, 4.1-4.1.22, 4.2-4.2.19, 4.3-4.3.15, 4.4-4.4.14, 4.5-4.5.13, 4.6-4.6.10, 4.7-4.7.9, 4.8-4.8.5, 4.9-4.9.4
3.7.26, 3.8.26, 3.9.24, 4.0.23, 4.1.23, 4.2.20, 4.3.16, 4.4.15, 4.5.14, 4.6.11, 4.7.10, 4.8.6, 4.9.5
03/04/2018
WordPress Core < 5.0 – Denial of Service
In WordPress before 5.0, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times. It…
[*, 5.0)
5.0
05/02/2018
Comprendre les données
Comment utiliser cet annuaire de vulnérabilités ?
Chaque fiche associe une vulnérabilité à un composant précis, avec sa gravité, les versions affectées et les versions corrigées lorsqu’elles sont connues. Les pages de wordpress servent de point d’entrée pour retrouver rapidement les composants concernés.
Une CVE ne signifie pas automatiquement qu’un site a été compromis. Elle indique qu’une version donnée peut être exposée. La bonne démarche consiste à vérifier l’inventaire réel, sauvegarder, mettre à jour, puis contrôler le fonctionnement et les journaux du site.
WP Commander
Rechercher dans toute la base WordPress
Utilisez la recherche globale pour retrouver une extension, un thème, une CVE ou un identifiant de vulnérabilité.