WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Vendor wordpress✕
Overview 20 matches · 0 in Waratek scope · 0 protected · 5 exploited · 2 CISA KEV · 3 public PoC · 2 EPSS ≥ 0.5
20matches 0in Waratek scope0.0% 0protected0.0% 5exploited25.0% 2CISA KEV10.0% 3public PoC15.0% 2EPSS ≥ 0.510.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% Outside Waratek scope 1 5.0% Not applicable 19 95.0% Withdrawn CVE 0 0.0%
Critical 20 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 20 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 5 25.0% Working exploit published 1 5.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 14 70.0%
split by peak 5 / year
Not applicable: 19Outside Waratek scope: 1 Critical: 20 not blocked: 20 No public exploit: 14Working exploit published: 1Exploited: 5
20071 Not applicable1 Critical1 not blocked1 No public exploit1 20080 20090 20100 20110 20120 20130 20140 20150 20162 Not applicable2 Critical2 not blocked2 Exploited1 Working exploit published1 20173 Outside Waratek scope1 Not applicable2 Critical3 not blocked3 Exploited2 No public exploit1 20181 Not applicable1 Critical1 not blocked1 No public exploit1 20193 Not applicable3 Critical3 not blocked3 No public exploit3 20205 Not applicable5 Critical5 not blocked5 No public exploit5 20213 Not applicable3 Critical3 not blocked3 Exploited1 No public exploit2 20220 20230 20241 Not applicable1 Critical1 not blocked1 No public exploit1 20250 20261 Not applicable1 Critical1 not blocked1 Exploited1
2008201020122014201620182020202220242026
20 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2026-63030 Critical 2026-07-17 Not applicable Exploited WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue which, combined with the author__not_in WP_Query SQL Injection (CVE-2026-60137), could allow an attacker to perform SQL Injection and achieve Remote Code Execution.
CVE-2024-31211 Critical 2024-04-04 Not applicable No public exploit WordPress is an open publishing platform for the Web. Unserialization of instances of the `WP_HTML_Token` class allows for code execution via its `__destruct()` magic method. This issue was fixed in WordPress 6.4.2 on December 6th, 2023. Versions prior to 6.4.0 are not affected.
CVE-2021-44223 Critical 2021-11-25 Not applicable No public exploit WordPress before 5.8 lacks support for the Update URI plugin header. This makes it easier for remote attackers to execute arbitrary code via a supply-chain attack against WordPress installations that use any plugin for which the slug satisfies the naming constraints of the WordPress.org Plugin Directory but is not yet present in that directory.
CVE-2020-36326 Critical 2021-04-28 Not applicable No public exploit PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.
CVE-2021-29476 Critical 2021-04-27 Not applicable Exploited Requests is a HTTP library written in PHP. Requests mishandles deserialization in FilteredIterator. The issue has been patched and users of `Requests` 1.6.0, 1.6.1 and 1.7.0 should update to version 1.8.0.
CVE-2020-28039 Critical 2020-11-02 Not applicable No public exploit is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected.
CVE-2020-28037 Critical 2020-11-02 Not applicable No public exploit is_blog_installed in wp-includes/functions.php in WordPress before 5.5.2 improperly determines whether WordPress is already installed, which might allow an attacker to perform a new installation, leading to remote code execution (as well as a denial of service for the old installation).
CVE-2020-28036 Critical 2020-11-02 Not applicable No public exploit wp-includes/class-wp-xmlrpc-server.php in WordPress before 5.5.2 allows attackers to gain privileges by using XML-RPC to comment on a post.
CVE-2020-28035 Critical 2020-11-02 Not applicable No public exploit WordPress before 5.5.2 allows attackers to gain privileges via XML-RPC.
CVE-2020-28032 Critical 2020-11-02 Not applicable No public exploit WordPress before 5.5.2 mishandles deserialization requests in wp-includes/Requests/Utility/FilteredIterator.php.
CVE-2019-20041 Critical 2019-12-27 Not applicable No public exploit wp_kses_bad_protocol in wp-includes/kses.php in WordPress before 5.3.1 mishandles the HTML5 colon named entity, allowing attackers to bypass input sanitization, as demonstrated by the javascript: substring.
CVE-2019-17670 Critical 2019-10-17 Not applicable No public exploit WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs.
CVE-2019-17669 Critical 2019-10-17 Not applicable No public exploit WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
CVE-2018-20148 Critical 2018-12-14 Not applicable No public exploit In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could conduct PHP object injection attacks via crafted metadata in a wp.getMediaItem XMLRPC call. This is caused by mishandling of serialized data at phar:// URLs in the wp_get_attachment_thumb_file function in wp-includes/post.php.
CVE-2017-16510 Critical 2017-11-02 Not applicable No public exploit 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-2017-14723 Critical 2017-09-23 Not applicable Exploited 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 Critical 2017-01-30 Outside Waratek scope Exploited 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-2016-10045 Critical 2016-12-30 Not applicable Working exploit published 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-2016-10033 Critical 2016-12-30 Not applicable Exploited 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-2007-6013 Critical 2007-11-19 Not applicable No public exploit 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.