7 matches found
CVE-2026-26273
Known is a social publishing platform. Prior to 1.6.3, a Critical Broken Authentication vulnerability exists in Known 1.6.2 and earlier. The application leaks the password reset token within a hidden HTML input field on the password reset page. This allows any unauthenticated attacker to retrieve...
CVE-2026-26273
Known is a social publishing platform. Prior to 1.6.3, a Critical Broken Authentication vulnerability exists in Known 1.6.2 and earlier. The application leaks the password reset token within a hidden HTML input field on the password reset page. This allows any unauthenticated attacker to retrieve...
CVE-2026-26273 Known affected by Account Takeover via Password Reset Token Leakage
Known is a social publishing platform. Prior to 1.6.3, a Critical Broken Authentication vulnerability exists in Known 1.6.2 and earlier. The application leaks the password reset token within a hidden HTML input field on the password reset page. This allows any unauthenticated attacker to retrieve...
Known 授权问题漏洞
Known is a known open-source social publishing platform in the United States. Versions prior to 1.6.3 of Known had an authorization issue vulnerability. This vulnerability stemmed from the leakage of the password reset token through a hidden HTML input field on the password reset page, which coul...
Known 安全漏洞
Known is a social publishing platform open-sourced by Known in the United States. A security vulnerability exists in Known v1.3.1 and below, which stems from the discovery of the inclusion of an unsafe direct object reference IDOR...
Known 跨站脚本漏洞
Known is an American Known open source social publishing platform. A security vulnerability exists in Known v1.3.1 and below, which stems from the presence of a cross-site scripting XSS vulnerability that allows an authenticated attacker to execute arbitrary web script or HTML via a crafted paylo...
Known 跨站脚本漏洞
Known is a social publishing platform open-sourced by Known in the United States. A security vulnerability exists in Known v1.3.1 and below, which stems from an issue with the isSVG function that allows an attacker to execute arbitrary code via a crafted SVG file...