Aggregates CVE and security vulnerability intelligence across all WordPress-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Historical issues mainly involve vendor risk sql injection, vendor risk csrf, vendor risk input validation, and vendor risk open redirect and related problems; some flaws may lead to vendor impact data exposure.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2012-6707 | 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 | [email protected] | 7.5 | 1.11% | 2017-10-19 | 2026-06-16 |
| CVE-2016-9263 | 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. | [email protected] | 4.7 | 2.55% | 2017-10-12 | 2026-06-16 |
| CVE-2017-14990 | 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 vulnerability). | [email protected] | 6.5 | 1.76% | 2017-10-02 | 2026-06-16 |
| CVE-2017-14726 | Before version 4.8.2, WordPress was vulnerable to a cross-site scripting attack via shortcodes in the TinyMCE visual editor. | [email protected] | 6.1 | 2.66% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14725 | 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. | [email protected] | 5.4 | 2.13% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14724 | Before version 4.8.2, WordPress was vulnerable to cross-site scripting in oEmbed discovery. | [email protected] | 6.1 | 2.86% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14723 | 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. | [email protected] | 9.8 | 10.43% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14722 | Before version 4.8.2, WordPress allowed a Directory Traversal attack in the Customizer component via a crafted theme filename. | [email protected] | 7.5 | 7.82% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14721 | Before version 4.8.2, WordPress allowed Cross-Site scripting in the plugin editor via a crafted plugin name. | [email protected] | 6.1 | 2.14% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14720 | Before version 4.8.2, WordPress allowed a Cross-Site scripting attack in the template list view via a crafted template name. | [email protected] | 6.1 | 2.14% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14719 | Before version 4.8.2, WordPress was vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components. | [email protected] | 7.5 | 13.38% | 2017-09-23 | 2026-06-16 |
| CVE-2017-14718 | Before version 4.8.2, WordPress was susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL. | [email protected] | 6.1 | 2.14% | 2017-09-23 | 2026-06-16 |
| CVE-2017-9066 | In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF. | [email protected] | 8.6 | 3.67% | 2017-05-18 | 2026-06-16 |
| CVE-2017-9065 | In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API. | [email protected] | 7.5 | 4.08% | 2017-05-18 | 2026-06-16 |
| CVE-2017-9064 | 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. | [email protected] | 8.8 | 1.74% | 2017-05-18 | 2026-06-16 |
| CVE-2017-9063 | In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization session. | [email protected] | 6.1 | 2.00% | 2017-05-18 | 2026-06-16 |
| CVE-2017-9062 | In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API. | [email protected] | 8.6 | 1.77% | 2017-05-18 | 2026-06-16 |
| CVE-2017-9061 | 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. | [email protected] | 6.1 | 1.93% | 2017-05-18 | 2026-06-16 |
| CVE-2017-8295 | WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to transmission of the reset key to a mailbox on an attacker-controlled SMTP server. This is related to problematic use of the SERVER_NAME variable in wp-includes/pluggable.php in conjunction with the PHP ma | [email protected] | 5.9 | 26.70% | 2017-05-04 | 2026-06-16 |
| CVE-2017-1001000 | 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. | 46fe6300-5254-4a98-9594-a9567bec8179 | 7.5 | 81.85% | 2017-04-02 | 2026-06-16 |