Répertoire de sécurité WordPress
Vulnérabilités du cœur WordPress, page 19
Consultez 380 vulnérabilités connues du cœur WordPress, avec CVE, gravité CVSS, versions affectées et correctifs disponibles. Page 19 de l’annuaire.
WordPress Core
Failles et CVE du cœur WordPress
WordPress Core < 2.0.3 – IP Address Spoofing
vars.php in WordPress 2.0.2, possibly when running on Mac OS X, allows remote attackers to spoof their IP address via a PC_REMOTE_ADDR HTTP header, which vars.php uses to redefine $_SERVER['REMOTE_ADDR'].
*-2.0.2
2.0.3
01/06/2006
WordPress Core <= 2.0.1 – Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in the "post comment" functionality of WordPress 2.0.1 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) name, (2) website, and (3) comment parameters.
*-2.0.1
2.0.2
10/03/2006
WordPress Core < 2.0.2 – Reflected Cross-Site Scripting
Multiple "unannounced" cross-site scripting (XSS) vulnerabilities in WordPress before 2.0.2 allow remote attackers to inject arbitrary web script or HTML via unknown attack vectors.
[*, 2.0.2)
2.0.2
10/03/2006
WordPress Core < 2.0.2 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in wp-register.php in WordPress 2.0 and 2.0.1 allows remote attackers to inject arbitrary web script or HTML via the user_email parameter.
[*, 2.0.2)
2.0.2
10/03/2006
WordPress Core < 2.0.2 – Sensitive Information Disclosure
WordPress 2.0.1 and earlier allows remote attackers to obtain sensitive information via a direct request to (1) default-filters.php, (2) template-loader.php, (3) rss-functions.php, (4) locale.php, (5) wp-db.php, and (6) kses.php in the wp-includes/ directory; and (7) edit-form-advanced.php, (8) admin-functions.php,…
*-2.0.1
2.0.2
10/03/2006
WordPress Core < 2.0.1 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in the paging links functionality in template-functions-links.php in Wordpress 1.5.2, and possibly other versions before 2.0.1, allows remote attackers to inject arbitrary web script or HTML to Internet Explorer users via the request URI…
*-2.0
2.0.1
31/01/2006
WordPress Core <= 1.5.2 – SQL Injection
SQL injection vulnerability in WordPress 1.5.2, and possibly other versions before 2.0, allows remote attackers to execute arbitrary SQL commands via the User-Agent field in an HTTP header for a comment.
*-1.5.2
2.0
31/12/2005
WordPress Core < 1.5.2 – Remote Code Execution
Direct code injection vulnerability in WordPress 1.5.1.3 and earlier allows remote attackers to execute arbitrary PHP code via the cache_lastpostdate[server] cookie.
*-1.5.1.3
1.5.2
09/08/2005
WordPress Core < 1.5.1.3 – Arbitrary Email Content Change
wp-login.php in WordPress 1.5.1.2 and earlier allows remote attackers to change the content of the forgotten password e-mail message via the message variable, which is not initialized before use.
*-1.5.1.2
1.5.1.3
29/06/2005
WordPress Core < 1.5.1.3 – Sensitive Information Disclosure
WordPress 1.5.1.2 and earlier allows remote attackers to obtain sensitive information via (1) a direct request to menu-header.php or a "1" value in the feed parameter to (2) wp-atom.php, (3) wp-rss.php, or (4) wp-rss2.php, which reveal the path…
*-1.5.1.2
1.5.1.3
29/06/2005
WordPress Core <= 1.5.1.2 – Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in post.php in WordPress 1.5.1.2 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) p or (2) comment parameter.
*-1.5.1.2
1.5.1.3
29/06/2005
WordPress Core < 1.5.1.3 – SQL Injection
SQL injection vulnerability in XMLRPC server in WordPress 1.5.1.2 and earlier allows remote attackers to execute arbitrary SQL commands via input that is not filtered in the HTTP_RAW_POST_DATA variable, which stores the data in an XML file.
[*, 1.5.1.3)
1.5.1.3
29/06/2005
WordPress Core <= 1.5 – Stored Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in template-functions-post.php in WordPress 1.5 and earlier allow remote attackers to execute arbitrary commands via the (1) content or (2) title of the post.
*-1.5.1
1.5.1.2
27/06/2005
WordPress Core < 1.5.1.2 – SQL Injection
SQL injection vulnerability in template-functions-category.php in WordPress 1.5.1 allows remote attackers to execute arbitrary SQL commands via the $cat_ID variable, as demonstrated using the cat parameter to index.php.
*-1.5.1.1
1.5.1.2
27/05/2005
WordPress Core < 1.5.1 – SQL Injection
SQL injection vulnerability in wp-trackback.php in Wordpress 1.5 and earlier allows remote attackers to execute arbitrary SQL commands via the tb_id parameter.
[*, 1.5.1)
1.5.1
09/05/2005
WordPress Core < 1.5.1 – Full Path Disclosure
Wordpress 1.5 and earlier allows remote attackers to obtain sensitive information via a direct request to files in (1) wp-content/themes/, (2) wp-includes/, or (3) wp-admin/, which reveal the path in an error message.
[*, 1.5.1)
1.5.1
09/05/2005
WordPress Core <= 1.2 – HTTP Response Splitting
CRLF injection vulnerability in wp-login.php in WordPress 1.2 allows remote attackers to perform HTTP Response Splitting attacks to modify expected HTML content from the server via the text parameter.
[*, 1.2.1)
1.2.1
06/10/2004
WordPress Core < 1.2.1 – Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in Wordpress 1.2 allow remote attackers to inject arbitrary web script or HTML via the (1) redirect_to, text, popupurl, or popuptitle parameters to wp-login.php, (2) redirect_url parameter to admin-header.php, (3) popuptitle, popupurl, content,…
[*, 1.2)
1.2
06/10/2004
WordPress Core < 0.72 – SQL Injection
SQL injection vulnerability in log.header.php in WordPress 0.7 and earlier allows remote attackers to execute arbitrary SQL commands via the posts variable.
[*, 0.72)
0.72
11/10/2003
WordPress Core <= 0.70 – Remote File Inclusion
PHP remote file inclusion vulnerability in wp-links/links.all.php in WordPress 0.70 allows remote attackers to execute arbitrary PHP code via a URL in the $abspath variable.
*-0.70
0.71
09/06/2003
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é.