Vulnerabilidades exploráveis hoje
419,150na visualização atual
Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.
No catálogo KEV1,790
Novos KEV · 24H0
Exploit Today ≥ 701,719
Distribuição · última janela
- Crítica4,738
- Alta18,320
- Média18,080
- Baixa1,972
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2017-15993—86.0%
——26——CVE-2018-5978—86.0%
——26——CVE-2026-98347.2 ALT86.0%
——26The WP Database Backup – Unlimited Database & Files Backup by Backup for WP plugin for WordPress is vulnerable to OS Command Injection in all versions up to and including 7.11 via the `wp_db_exclude_table` parameter. This is due to the direct concatenation of user-supplied `$_POST['wp_db_exclude_table']` values into the `mysqldump` shell command string in the `mysqldump()` function of `includes/admin/class-wpdb-admin.php` without wrapping them in `escapeshellarg()`—every other argument in the same command (DB_USER, DB_PASSWORD, host, filename, DB_NAME) is properly escaped, making the exclude-table values the sole exception—and because the only applied filtering, `sanitize_text_field()` via `recursive_sanitize_text_field()`, strips HTML tags but leaves shell metacharacters such as `;`, `|`, `` ` ``, and `$()` intact. This makes it possible for authenticated attackers, with administrator-level access and above, to execute arbitrary operating system commands on the server, potentially enabling full remote code execution. The injection is stored: malicious values submitted through the plugin settings form are persisted to the WordPress options table via `update_option('wp_db_exclude_table')` and later retrieved with `get_option()` and passed unsanitized to `shell_exec()` whenever a backup operation runs.142dCVE-2007-0850—86.0%
——26——CVE-2018-5971—86.0%
——26——CVE-2014-7912—86.0%
——26——CVE-2018-5974—86.0%
——26——CVE-2018-5970—86.0%
——26——CVE-2008-5685—86.0%
——26——CVE-2021-2479—86.0%
——26——CVE-2016-7179—86.0%
——26——CVE-2017-17875—86.0%
——26——CVE-2018-6004—86.0%
——26——CVE-2026-22224—86.0%
——26——CVE-2005-0232—86.0%
——26——CVE-2018-5993—86.0%
——26——CVE-2005-1925—86.0%
——26——CVE-2009-0842—86.0%
——26——CVE-2021-31590—86.0%
——26——CVE-2009-0673—86.0%
——26——CVE-2019-14457—86.0%
——26——CVE-2021-3621—86.0%
——26——CVE-2002-2258—86.0%
——26——CVE-2008-1854—86.0%
——26——CVE-2017-7602—86.0%
——26——CVE-2014-8119—86.0%
——26——CVE-2018-14638—86.0%
——26——CVE-2018-6576—86.0%
——26——CVE-2019-6772—86.0%
——26——CVE-2017-15977—86.0%
——26——CVE-2018-6604—86.0%
——26——CVE-2017-15979—86.0%
——26——CVE-2018-7177—86.0%
——26——CVE-2018-7179—86.0%
——26——CVE-2018-15769—86.0%
——26——CVE-2009-5016—86.0%
——26——CVE-2016-3539—86.0%
——26——CVE-2008-0949—86.0%
——26——CVE-2018-6394—86.0%
——26——CVE-2018-6395—86.0%
——26——