Vulnerabilidades exploráveis hoje
413,805na 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,779
Novos KEV · 24H0
Exploit Today ≥ 701,707
Distribuição · última janela
- Crítica5,594
- Alta22,456
- Média20,779
- Baixa2,126
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2012-4301—95.0%
——28——CVE-2002-0483—95.0%
——28——CVE-2009-1788—95.0%
——28——CVE-2015-2368—95.0%
——28——CVE-2019-0548—95.0%
——28——CVE-2020-9488—95.0%
——28——CVE-2026-84387.2 ALT95.0%
——28The All-In-One Security (AIOS) – Security and Firewall plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 5.4.7. This is due to insufficient input sanitization in the get_rest_route() function and missing output escaping in the column_default() method of the debug log list table. When the 'Disable REST API for non-logged in users' feature (aiowps_disallow_unauthorized_rest_requests) is enabled alongside debug logging (aiowps_enable_debug), an unauthenticated attacker can embed arbitrary HTML or JavaScript in the REST request path. The path is retrieved via urldecode($_SERVER['REQUEST_URI']), which decodes URL-encoded payloads into literal HTML characters. This decoded, unsanitized value is concatenated directly into a debug log message and stored in the database. When an administrator navigates to the AIOS Dashboard Debug Logs page, the column_default() method returns the raw database value without escaping, and the parent list table echoes it directly, causing JavaScript execution in the administrator's browser session. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator views the debug log page, enabling nonce theft, privileged AJAX/REST actions, and potential full site compromise.113dCVE-2006-6143—95.0%
——28——CVE-2008-7269—95.0%
——28——CVE-2018-20182—95.0%
——28——CVE-2017-8522—95.0%
——28——CVE-2015-1561—95.0%
——28——CVE-2004-0642—95.0%
——28——CVE-2011-0284—95.0%
——28——CVE-2009-2204—95.0%
——28——CVE-2024-40348—95.0%
——28——CVE-2018-1000773—95.0%
——28——CVE-2020-8853—95.0%
——28——CVE-2019-8271—95.0%
——28——CVE-2013-0612—94.9%
——28——CVE-2009-0418—94.9%
——28——CVE-2003-0118—94.9%
——28——CVE-2020-10967—94.9%
——28——CVE-2016-3963—94.9%
——28——CVE-2016-7251—94.9%
——28——CVE-2018-15172—94.9%
——28——CVE-2006-3475—94.9%
——28——CVE-2019-16645—94.9%
——28——CVE-2021-39165—94.9%
——28——CVE-2017-9614—94.9%
——28——CVE-2010-1478—94.9%
——28——CVE-2012-4354—94.9%
——28——CVE-2018-10184—94.9%
——28——CVE-2007-3621—94.9%
——28——CVE-2020-8877—94.9%
——28——CVE-2006-0922—94.9%
——28——CVE-2006-0527—94.9%
——28——CVE-2016-3276—94.9%
——28——CVE-2019-11369—94.9%
——28——CVE-2010-1473—94.9%
——28——