Vulnerabilidades exploráveis hoje
419,033na 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,786
Novos KEV · 24H0
Exploit Today ≥ 701,715
Distribuição · última janela
- Crítica4,738
- Alta18,314
- Média18,069
- Baixa1,978
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2020-25136—87.5%
——26——CVE-2025-21219—87.5%
——26——CVE-2018-19432—87.5%
——26——CVE-2022-24461—87.5%
——26——CVE-2017-12928—87.5%
——26——CVE-2026-76937.2 ALT87.5%
——26The Backup Migration plugin for WordPress is vulnerable to OS Command Injection in all versions up to, and including, 2.1.5.1 due to insufficient sanitization of the `file` POST parameter on the `restoreBackup()` AJAX handler. The handler applies `esc_attr()` — an HTML-context sanitizer that does not strip shell metacharacters — and concatenates the result, unquoted, into a `php-cli -f … bmi_restore <file> <remote>` command passed to `exec()`. This makes it possible for authenticated attackers, with Administrator-level access (or any user granted the plugin's `do_backups` capability) and above, to execute arbitrary OS commands as the web-server user, bypassing WordPress hardening constants such as `DISALLOW_FILE_EDIT` and `DISALLOW_FILE_MODS` that would otherwise prevent code execution from the admin UI. This is an incomplete fix of CVE-2023-7002, which patched the same pattern only in the `$_POST['url']` path of `handleQuickMigration()`; the equivalent mitigations (`rawurlencode()` + explicit shell-metachar replacement + double-quoting in `exec()`) were never applied to `$backupName`.100dCVE-2016-5101—87.5%
——26——CVE-2004-2475—87.5%
——26——CVE-2013-2293—87.5%
——26——CVE-2020-13946—87.5%
——26——CVE-2017-1440—87.5%
——26——CVE-2022-24171—87.5%
——26——CVE-2022-24168—87.5%
——26——CVE-2022-26994—87.5%
——26——CVE-2024-8077—87.5%
——26——CVE-2013-4077—87.5%
——26——CVE-2015-1242—87.5%
——26——CVE-2006-3194—87.5%
——26——CVE-2008-2441—87.5%
——26——CVE-2017-6089—87.5%
——26——CVE-2008-2053—87.5%
——26——CVE-2015-1775—87.5%
——26——CVE-2019-20424—87.5%
——26——CVE-2008-5526—87.5%
——26——CVE-2022-24170—87.5%
——26——CVE-2011-2725—87.5%
——26——CVE-2017-17067—87.5%
——26——CVE-2009-3362—87.5%
——26——CVE-2018-4056—87.5%
——26——CVE-2017-9937—87.5%
——26——CVE-2016-5254—87.5%
——26——CVE-2017-11323—87.5%
——26——CVE-2008-4077—87.4%
——26——CVE-2009-1958—87.4%
——26——CVE-2018-15890—87.4%
——26——CVE-2016-8877—87.4%
——26——CVE-2005-0366—87.4%
——26——CVE-2013-1437—87.4%
——26——CVE-2021-23406—87.4%
——26——CVE-2010-0856—87.4%
——26——