Répertoire de sécurité WordPress
Vulnérabilités du cœur WordPress, page 18
Consultez 380 vulnérabilités connues du cœur WordPress, avec CVE, gravité CVSS, versions affectées et correctifs disponibles. Page 18 de l’annuaire.
WordPress Core
Failles et CVE du cœur WordPress
WordPress Core < 2.09 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in the wp_explain_nonce function in the nonce AYS functionality (wp-includes/functions.php) for WordPress 2.0 before 2.0.9 and 2.1 before 2.1.1 allows remote attackers to inject arbitrary web script or HTML via the file parameter to…
[*, 2.0.9), 2.1
2.0.9, 2.1.1
21/02/2007
WordPress Core <= 3.0.4 – Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in WordPress before 3.0.5 allow remote authenticated users to inject arbitrary web script or HTML via vectors related to (1) the Quick/Bulk Edit title (aka post title or post_title), (2) post_status, (3) comment_status,…
*-3.0.4
3.0.5
11/02/2007
WordPress Core < 2.1 – Directory Traversal
WordPress allows remote attackers to determine the existence of arbitrary files, and possibly read portions of certain files, via pingback service calls with a source URI that corresponds to a local pathname, which triggers different fault codes for…
[*, 2.1)
2.1
24/01/2007
WordPress Core < 2.1 – Denial of Service
The wp_remote_fopen function in WordPress before 2.1 allows remote attackers to cause a denial of service (bandwidth or thread consumption) via pingback service calls with a source URI that corresponds to a large file, which triggers a long…
[*, 2.1)
2.1
22/01/2007
WordPress Core < 2.1 – Full Path Disclosure
WordPress 2.0.11 and earlier allows remote attackers to obtain sensitive information via an empty value of the page parameter to certain PHP scripts under wp-admin/, which reveals the path in various error messages.
*-2.0.11
2.1
22/01/2007
WordPress Core < 2.0.7 – SQL Injection
wp-trackback.php in WordPress 2.0.6 and earlier does not properly unset variables when the input data includes a numeric parameter with a value matching an alphanumeric parameter's hash value, which allows remote attackers to execute arbitrary SQL commands via…
*-2.0.6
2.0.7
15/01/2007
WordPress Core < 2.0.7 – Full Path Disclosure
WordPress 2.0.6, and 2.1Alpha 3 (SVN:4662), does not properly verify that the m parameter value has the string data type, which allows remote attackers to obtain sensitive information via an invalid m[] parameter, as demonstrated by obtaining the…
*-2.0.6
2.0.7
15/01/2007
WordPress Core 2.0.2 – 2.0.5 – Sensitive Information Disclosure
WordPress 2.0.2 through 2.0.5 allows remote attackers to obtain sensitive information via a direct request for (1) 404.php, (2) akismet.php, (3) archive.php, (4) archives.php, (5) attachment.php, (6) blogger.php, (7) comments.php, (8) comments-popup.php, (9) dotclear.php, (10) footer.php, (11) functions.php,…
2.0.2-2.0.5
2.0.6
05/01/2007
WordPress Core <= 2.0.5 – SQL Injection
WordPress before 2.0.6, when mbstring is enabled for PHP, decodes alternate character sets after escaping the SQL query, which allows remote attackers to bypass SQL injection protection schemes and execute arbitrary SQL commands via multibyte charsets, as demonstrated…
*-2.0.5
2.0.6
05/01/2007
WordPress Core <= 2.0.5 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in wp-admin/templates.php in WordPress 2.0.5 allows remote attackers to inject arbitrary web script or HTML via the file parameter. NOTE: some sources have reported this as a vulnerability in the get_file_description function in wp-admin/admin-functions.php.
*-2.0.5
2.0.6
05/01/2007
WordPress Core <= 2.0.5 – Cross-Site Request Forgery to Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in the CSRF protection scheme in WordPress before 2.0.6 allows remote attackers to inject arbitrary web script or HTML via a CSRF attack with an invalid token and quote characters or HTML tags in…
*-2.0.5
2.0.6
05/01/2007
WordPress < 2.0.6 – Username Enumeration via Error Messages
wp-login.php in WordPress 2.0.5 and earlier displays different error messages if a user exists or not, which allows remote attackers to obtain sensitive information and facilitates brute force attacks.
*-2.0.5
2.0.6
05/01/2007
WordPress Core <= 2.0.4 – Denial of Service
WordPress before 2.0.5 does not properly store a profile containing a string representation of a serialized object, which allows remote authenticated users to cause a denial of service (application crash) via a string that represents a (1) malformed…
*-2.0.4
2.0.5
27/10/2006
WordPress Core <= 2.0.4 – Directory Traversal
Multiple directory traversal vulnerabilities in plugins/wp-db-backup.php in WordPress before 2.0.5 allow remote authenticated users to read or overwrite arbitrary files via directory traversal sequences in the (1) backup and (2) fragment parameters in a GET request.
*-2.0.4
2.0.5
27/10/2006
WordPress Core < 2.0.5 – User Metadata Information Disclosure
wp-admin/user-edit.php in WordPress before 2.0.5 allows remote authenticated users to read the metadata of an arbitrary user via a modified user_id parameter.
*-2.0.4
2.0.5
18/09/2006
WordPress Core < 1.5.2 – Full Path Disclosure
WordPress before 1.5.2 allows remote attackers to obtain sensitive information via a direct request to (1) wp-includes/vars.php, (2) wp-content/plugins/hello.php, (3) wp-admin/upgrade-functions.php, (4) wp-admin/edit-form.php, (5) wp-settings.php, and (6) wp-admin/edit-form-comment.php, which leaks the path in an error message related to…
[*, 1.5.2)
1.5.2
14/08/2006
WordPress Core <= 2.0.3 – Denial of Service
Directory traversal vulnerability in wp-db-backup.php in WordPress 2.0.3 and earlier allows remote attackers to read arbitrary files, delete arbitrary files, and cause a denial of service via a .. (dot dot) in the backup parameter in a wp-db-backup.php…
*-2.0.3
2.0.4
29/07/2006
WordPress Core < 2.0.4 – Full Path Disclosure
WordPress 2.0.3 allows remote attackers to obtain the installation path via a direct request to various files, such as those in the (1) wp-admin, (2) wp-content, and (3) wp-includes directories, possibly due to uninitialized variables.
*-2.0.3
2.0.4
29/07/2006
WordPress Core < 2.0.4 – Privilege Escalation
Multiple unspecified vulnerabilities in WordPress before 2.0.4 have unknown impact and remote attack vectors. NOTE: due to lack of details, it is not clear how these issues are different from CVE-2006-3389 and CVE-2006-3390, although it is likely that…
[*, 2.0.4)
2.0.4
09/07/2006
WordPress Core < 2.0.3 – Remote Code Execution
Direct static code injection vulnerability in WordPress 2.0.2 and earlier allows remote attackers to execute arbitrary commands by inserting a carriage return and PHP code when updating a profile, which is appended after a special comment sequence into…
*-2.0.2
2.0.3
01/06/2006
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é.