Vulnerabilidades exploráveis hoje
409,857na 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,769
Novos KEV · 24H0
Exploit Today ≥ 701,700
Distribuição · última janela
- Crítica5,527
- Alta21,042
- Média20,196
- Baixa2,086
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2023-20888—99.7%
——30——CVE-2021-2400—99.7%
——30——CVE-2024-10915—99.7%
——30——CVE-2021-25094—99.7%
——30——CVE-2021-44224—99.7%
——30——CVE-2023-1698—99.7%
——30——CVE-2011-2140—99.7%
——30——CVE-2021-29441—99.7%
——30——CVE-2003-0822—99.7%
——30——CVE-2023-40502—99.7%
——30——CVE-2003-0818—99.7%
——30——CVE-2020-7246—99.7%
——30——CVE-2014-4511—99.7%
——30——CVE-2022-36958—99.7%
——30——CVE-2025-584349.8 CRÍ99.7%
——30Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the `forgot-password` endpoint in Flowise returns sensitive information including a valid password reset `tempToken` without authentication or verification. This enables any attacker to generate a reset token for arbitrary users and directly reset their password, leading to a complete account takeover (ATO). This vulnerability applies to both the cloud service (`cloud.flowiseai.com`) and self-hosted/local Flowise deployments that expose the same API. Commit 9e178d68873eb876073846433a596590d3d9c863 in version 3.0.6 secures password reset endpoints. Several recommended remediation steps are available. Do not return reset tokens or sensitive account details in API responses. Tokens must only be delivered securely via the registered email channel. Ensure `forgot-password` responds with a generic success message regardless of input, to avoid user enumeration. Require strong validation of the `tempToken` (e.g., single-use, short expiry, tied to request origin, validated against email delivery). Apply the same fixes to both cloud and self-hosted/local deployments. Log and monitor password reset requests for suspicious activity. Consider multi-factor verification for sensitive accounts.39dCVE-2019-8942—99.7%
——30——CVE-2023-46263—99.7%
——30——CVE-2023-30253—99.7%
——30——CVE-2015-3090—99.7%
——30——CVE-2019-7254—99.7%
——30——CVE-2022-32214—99.7%
——30——CVE-2009-2521—99.7%
——30——CVE-2019-13372—99.7%
——30——CVE-2024-10400—99.7%
——30——CVE-2022-12927.3 ALT99.7%
——30The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).4dCVE-2018-0886—99.7%
——30——CVE-2015-6922—99.7%
——30——CVE-2019-1619—99.7%
——30——CVE-2020-27955—99.7%
——30——CVE-2022-42904—99.7%
——30——CVE-2016-0800—99.7%
——30——CVE-2015-8605—99.7%
——30——CVE-2020-17505—99.7%
——30——CVE-2022-28732—99.7%
——30——CVE-2020-2230—99.7%
——30——CVE-2015-6128—99.7%
——30——CVE-2023-38096—99.7%
——30——CVE-2004-0597—99.7%
——30——CVE-2016-0041—99.7%
——30——CVE-2012-0053—99.7%
——30——