CVE search
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
| 19/10/2017 |
| CVE-2016-9263 | 보통4.7 | WordPress through 4.8.2, when domain-based flashmediaelement.swf sandboxing is not used, allows remote attackers to conduct cross-domain Flash injection (XSF) attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file. | 12/10/2017 |
| CVE-2017-14990 | 보통6.5 | WordPress 4.8.2 stores cleartext wp_signups.activation_key values (but stores the analogous wp_users.user_activation_key values as hashes), which might make it easier for remote attackers to hijack unactivated user accounts by leveraging database read access (such as access gained through an unspecified SQL injection v | 03/10/2017 |
| CVE-2017-14726 | 보통6.1 | Before version 4.8.2, WordPress was vulnerable to a cross-site scripting attack via shortcodes in the TinyMCE visual editor. | 23/09/2017 |
| CVE-2017-14725 | 보통5.4 | Before version 4.8.2, WordPress was susceptible to an open redirect attack in wp-admin/edit-tag-form.php and wp-admin/user-edit.php. | 23/09/2017 |
| CVE-2017-14724 | 보통6.1 | Before version 4.8.2, WordPress was vulnerable to cross-site scripting in oEmbed discovery. | 23/09/2017 |
| CVE-2017-14723 | 심각9.8 | 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. | 23/09/2017 |
| CVE-2017-14722 | 높음7.5 | Before version 4.8.2, WordPress allowed a Directory Traversal attack in the Customizer component via a crafted theme filename. | 23/09/2017 |
| CVE-2017-14721 | 보통6.1 | Before version 4.8.2, WordPress allowed Cross-Site scripting in the plugin editor via a crafted plugin name. | 23/09/2017 |
| CVE-2017-14720 | 보통6.1 | Before version 4.8.2, WordPress allowed a Cross-Site scripting attack in the template list view via a crafted template name. | 23/09/2017 |
| CVE-2017-14719 | 높음7.5 | Before version 4.8.2, WordPress was vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components. | 23/09/2017 |
| CVE-2017-14718 | 보통6.1 | Before version 4.8.2, WordPress was susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL. | 23/09/2017 |
| CVE-2017-9066 | 높음8.6 | In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF. | 18/05/2017 |
| CVE-2017-9065 | 높음7.5 | In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API. | 18/05/2017 |
| CVE-2017-9064 | 높음8.8 | 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. | 18/05/2017 |
| CVE-2017-9063 | 보통6.1 | In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization session. | 18/05/2017 |
| CVE-2017-9062 | 높음8.6 | In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API. | 18/05/2017 |
| CVE-2017-9061 | 보통6.1 | In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability exists when attempting to upload very large files, because the error message does not properly restrict presentation of the filename. | 18/05/2017 |