Répertoire de sécurité WordPress
Vulnérabilités du cœur WordPress, page 16
Consultez 389 vulnérabilités connues du cœur WordPress, avec CVE, gravité CVSS, versions affectées et correctifs disponibles. Page 16 de l’annuaire.
WordPress Core
Failles et CVE du cœur WordPress
WordPress Core & WordPress MU < 2.8.1 – Username Enumeration
The forgotten mail interface in WordPress and WordPress MU before 2.8.1 exhibits different behavior for a password request depending on whether the user account exists, which allows remote attackers to enumerate valid usernames. NOTE: the vendor reportedly disputes…
*-2.8
2.8.1
09/07/2009
WordPress Core < 2.8 – Sensitive Information Disclosure
WordPress 2.7.1 places the username of a post's author in an HTML comment, which allows remote attackers to obtain sensitive information by reading the HTML source.
*-2.7.1
2.8
11/06/2009
WordPress MU < 2.7 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in the choose_primary_blog function in wp-includes/wpmu-functions.php in WordPress MU (WPMU) before 2.7 allows remote attackers to inject arbitrary web script or HTML via the HTTP Host header.
[*, 2.7)
2.7
10/03/2009
WordPress Core < 2.6.5 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in the self_link function in in the RSS Feed Generator (wp-includes/feed.php) for WordPress before 2.6.5 allows remote attackers to inject arbitrary web script or HTML via the Host header (HTTP_HOST variable).
*-2.6.4
2.6.5
25/12/2008
WordPress Core < 2.8.1 – Open Redirect
Open redirect vulnerability in wp-admin/upgrade.php in WordPress, probably 2.6.x, allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the backto parameter.
[*, 2.8.1)
2.8.1
22/12/2008
WordPress Core < 2.7 – Denial of Service
wp-admin/upgrade.php in WordPress up to and including 2.6.1, allows remote attackers to upgrade the application, and possibly cause a denial of service (application outage), via a direct request if WordPress is not yet setup by creating an empty…
*-2.6.1
2.7
22/12/2008
WordPress Core < 2.6.2 – Cryptographic Weakness
The (1) rand and (2) mt_rand functions in PHP 5.2.6 do not produce cryptographically strong random numbers, which allows attackers to leverage exposures in products that rely on these functions for security-relevant functionality, as demonstrated by the password-reset…
*-2.6.1
2.6.2
08/09/2008
WordPress Core < 2.6.2 – Arbitrary User Password Reset
WordPress before 2.6.2 does not properly handle MySQL warnings about insertion of username strings that exceed the maximum column width of the user_login column, and does not properly handle space characters when comparing usernames, which allows remote attackers…
*-2.6.1
2.6.2
08/09/2008
WordPress MU < 2.6 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in wp-admin/wp-blogs.php in Wordpress MU (WPMU) before 2.6 allows remote attackers to inject arbitrary web script or HTML via the (1) s and (2) ip_address parameters.
[*, 2.6)
2.6
01/09/2008
WordPress Core < 2.6.1 – Cryptographic Weakness
The (1) get_edit_post_link and (2) get_edit_comment_link functions in wp-includes/link-template.php in WordPress before 2.6.1 do not force SSL communication in the intended situations, which might allow remote attackers to gain administrative access by sniffing the network for a cookie.
*-2.6
2.6.1
15/08/2008
WordPress Core < 2.6 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in WordPress before 2.6, SVN development versions only, allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
[*, 2.6)
2.6
15/07/2008
WordPress Core <= 2.5.1 – Arbitrary File Upload
Unrestricted file upload vulnerability in WordPress 2.5.1 and earlier might allow remote authenticated administrators to upload and execute arbitrary PHP files via the Upload section in the Write Tabs area of the dashboard.
*-2.5.1
2.5.2
25/04/2008
WordPress Core <= 2.5 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in WordPress 2.5 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
*-2.5
2.5.1
25/04/2008
WordPress Core <= 2.3.3 – Directory Traversal
Directory traversal vulnerability in the get_category_template function in wp-includes/theme.php in WordPress 2.3.3 and earlier, and 2.5, allows remote attackers to include and possibly execute arbitrary PHP files via the cat parameter in index.php. NOTE: some of these details…
*-2.3.3, 2.5
2.5.1
25/04/2008
WordPress Core < 2.5.1 – Authentication Bypass
The cookie authentication method in WordPress 2.5 relies on a hash of a concatenated string containing USERNAME and EXPIRY_TIME, which allows remote attackers to forge cookies by registering a username that results in the same concatenated string, as…
*-2.5
2.5.1
25/04/2008
WordPress Core <= 2.3.2 – Cross-Site Scripting
Multiple cross-site scripting (XSS) vulnerabilities in WordPress 2.3.2 allow remote attackers to inject arbitrary web script or HTML via the (1) inviteemail parameter in an invite action to wp-admin/users.php and the (2) to parameter in a sent action…
*-2.3.2
2.3.3
05/02/2008
WordPress Core 1.5 – 2.3.1 – Authorization Bypass
Wordpress 1.5 through 2.3.1 uses cookie values based on the MD5 hash of a password MD5 hash, which allows attackers to bypass authentication by obtaining the MD5 hash from the user database, then generating the authentication cookie from…
1.5-2.3.1
2.3.2
29/12/2007
WordPress Core < 2.5 – Full Path Disclosure
WordPress 2.2.x and 2.3.x allows remote attackers to obtain sensitive information via an invalid p parameter in an rss2 action to the default URI, which reveals the full path and the SQL database structure.
*-2.4
2.5
16/12/2007
WordPress Core <= 2.3 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in wp-admin/edit-post-rows.php in WordPress 2.3 allows remote attackers to inject arbitrary web script or HTML via the posts_columns array parameter.
*-2.3
2.3.1
26/10/2007
WordPress Core < 2.0.4 – Cross-Site Scripting
Cross-site scripting (XSS) vulnerability in wp-register.php in WordPress 2.0 allows remote attackers to inject arbitrary web script or HTML via the user_login parameter.
*-2.0.3
2.0.4
21/09/2007
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é.