PULSE
FEED
CVE Watch417.266 no arquivo completo

Vulnerabilidades exploráveis hoje

417,266na 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,782
Novos KEV · 24H0
Exploit Today ≥ 701,710

Distribuição · última janela

  • Crítica
    4,725
  • Alta
    18,177
  • Média
    17,809
  • Baixa
    1,945
Filtros
Filtros

Janela

Severidade

Filtros

Vulnerabilidades44,721–44,760 · 417,266
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2015-8384—
89.1%
——27——
CVE-2019-11941—
89.1%
——27——
CVE-2025-9934—
89.1%
——27——
CVE-2014-4461—
89.1%
——27——
CVE-2004-0426—
89.1%
——27——
CVE-2020-7195—
89.1%
——27——
CVE-2020-7191—
89.1%
——27——
CVE-2020-7184—
89.1%
——27——
CVE-2013-1739—
89.1%
——27——
CVE-2020-14072—
89.1%
——27——
CVE-2026-857149.1 CRÍ
89.1%
——27Stirling-PDF is a locally hosted web application that facilitates various operations on PDF files. Prior to 2.13.2, an authenticated administrator using the default H2 database and security mode can upload a crafted SQL file to POST /api/v1/database/import-database. DatabaseService.validateSqlContent() splits normalized input on semicolons and accepts a statement when it contains any allowed keyword, allowing dangerous H2 functions such as FILE_READ and CSVWRITE, plus CREATE ALIAS, to bypass the insufficient whitelist and execute side effects when RUNSCRIPT processes the file. This permits arbitrary file access. The demonstrated operating-system command execution chain writes attacker-controlled startup files to a user-site location and then triggers an application Python interpreter configured to load those startup files, resulting in command execution as the JVM service account. This issue is fixed in version 2.13.2.34d
CVE-2014-4243—
89.1%
——27——
CVE-2005-0126—
89.1%
——27——
CVE-2012-0667—
89.1%
——27——
CVE-2009-3841—
89.1%
——27——
CVE-2011-4186—
89.1%
——27——
CVE-2020-1209—
89.1%
——27——
CVE-2015-4230—
89.1%
——27——
CVE-2019-1754—
89.1%
——27——
CVE-2008-3808—
89.1%
——27——
CVE-2022-38649—
89.1%
——27——
CVE-2007-0665—
89.1%
——27——
CVE-2019-5338—
89.1%
——27——
CVE-2020-7175—
89.1%
——27——
CVE-2012-1735—
89.0%
——27——
CVE-2011-5059—
89.1%
——27——
CVE-2018-3608—
89.1%
——27——
CVE-2011-0836—
89.1%
——27——
CVE-2022-2825—
89.1%
——27——
CVE-2020-14573—
89.1%
——27——
CVE-2019-5374—
89.1%
——27——
CVE-2024-24402—
89.1%
——27——
CVE-2004-2284—
89.1%
——27——
CVE-2016-0093—
89.1%
——27——
CVE-2020-19363—
89.1%
——27——
CVE-2014-5109—
89.1%
——27——
CVE-2008-3608—
89.1%
——27——
CVE-2015-4145—
89.1%
——27——
CVE-2014-2647—
89.1%
——27——
CVE-2011-3459—
89.1%
——27——