WordPress
Sign in to watchby WordPress
CVEs (264)
| CVE | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2016-10033 | Cri | 0.79 | 9.8 | 0.94 | KEV | Dec 30, 2016 | The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \" (backslash double quote) in a crafted Sender property. |
| CVE-2016-10045 | Cri | 0.74 | 9.8 | 0.93 | Dec 30, 2016 | The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code by leveraging improper interaction between the escapeshellarg function and internal escaping performed in the mail function in PHP. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-10033. | |
| CVE-2017-14723 | Cri | 0.65 | 9.8 | 0.10 | Sep 23, 2017 | Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare, and thus did not properly address the possibility of plugins and themes enabling SQL injection attacks. | |
| CVE-2017-5611 | Cri | 0.65 | 9.8 | 0.12 | Jan 30, 2017 | SQL injection vulnerability in wp-includes/class-wp-query.php in WP_Query in WordPress before 4.7.2 allows remote attackers to execute arbitrary SQL commands by leveraging the presence of an affected plugin or theme that mishandles a crafted post type name. | |
| CVE-2017-16510 | Cri | 0.64 | 9.8 | 0.04 | Nov 2, 2017 | WordPress before 4.8.3 is affected by an issue where $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi) in plugins and themes, as demonstrated by a "double prepare" approach, a different vulnerability than CVE-2017-14723. | |
| CVE-2007-6013 | Cri | 0.64 | 9.8 | 0.02 | Nov 19, 2007 | 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 that hash. | |
| CVE-2017-17091 | Hig | 0.58 | 8.8 | 0.04 | Dec 2, 2017 | wp-admin/user-new.php in WordPress before 4.9.1 sets the newbloguser key to a string that can be directly derived from the user ID, which allows remote attackers to bypass intended access restrictions by entering this string. | |
| CVE-2017-1001000 | Hig | 0.58 | 7.5 | 0.79 | Apr 3, 2017 | The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a numeric value and a non-numeric value, as demonstrated by the wp-json/wp/v2/posts/123?id=123helloworld URI. | |
| CVE-2017-9064 | Hig | 0.57 | 8.8 | 0.01 | May 18, 2017 | In WordPress before 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is not required for updating credentials. | |
| CVE-2017-5489 | Hig | 0.57 | 8.8 | 0.01 | Jan 15, 2017 | Cross-site request forgery (CSRF) vulnerability in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving a Flash file upload. | |
| CVE-2017-9066 | Hig | 0.56 | 8.6 | 0.01 | May 18, 2017 | In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF. | |
| CVE-2017-9062 | Hig | 0.56 | 8.6 | 0.02 | May 18, 2017 | In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API. | |
| CVE-2016-2222 | Hig | 0.56 | 8.6 | 0.05 | May 22, 2016 | The wp_http_validate_url function in wp-includes/http.php in WordPress before 4.4.2 allows remote attackers to conduct server-side request forgery (SSRF) attacks via a zero value in the first octet of an IPv4 address in the u parameter to wp-admin/press-this.php. | |
| CVE-2017-14719 | Hig | 0.53 | 7.5 | 0.51 | Sep 23, 2017 | Before version 4.8.2, WordPress was vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components. | |
| CVE-2017-14722 | Hig | 0.51 | 7.5 | 0.31 | Sep 23, 2017 | Before version 4.8.2, WordPress allowed a Directory Traversal attack in the Customizer component via a crafted theme filename. | |
| CVE-2012-6707 | Hig | 0.49 | 7.5 | 0.00 | Oct 19, 2017 | WordPress through 4.8.2 uses a weak MD5-based password hashing algorithm, which makes it easier for attackers to determine cleartext values by leveraging access to the hash values. NOTE: the approach to changing this may not be fully compatible with certain use cases, such as migration of a WordPress site from a web host that uses a recent PHP version to a different web host that uses PHP 5.2. These use cases are plausible (but very unlikely) based on statistics showing widespread deployment of WordPress with obsolete PHP versions. | |
| CVE-2017-9065 | Hig | 0.49 | 7.5 | 0.04 | May 18, 2017 | In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API. | |
| CVE-2016-5839 | Hig | 0.49 | 7.5 | 0.01 | Jun 29, 2016 | WordPress before 4.5.3 allows remote attackers to bypass the sanitize_file_name protection mechanism via unspecified vectors. | |
| CVE-2016-5838 | Hig | 0.49 | 7.5 | 0.02 | Jun 29, 2016 | WordPress before 4.5.3 allows remote attackers to bypass intended password-change restrictions by leveraging knowledge of a cookie. | |
| CVE-2016-5837 | Hig | 0.49 | 7.5 | 0.01 | Jun 29, 2016 | WordPress before 4.5.3 allows remote attackers to bypass intended access restrictions and remove a category attribute from a post via unspecified vectors. |