Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-26273: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in idno known

0
Critical
VulnerabilityCVE-2026-26273cvecve-2026-26273cwe-200cwe-640
Published: Fri Feb 13 2026 (02/13/2026, 21:45:41 UTC)
Source: CVE Database V5
Vendor/Project: idno
Product: known

Description

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 the reset token for any user by simply querying the user's email, leading to full Account Takeover (ATO) without requiring access to the victim's email inbox. This vulnerability is fixed in 1.6.3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/20/2026, 22:32:28 UTC

Technical Analysis

CVE-2026-26273 is a critical security vulnerability discovered in the Known social publishing platform, specifically affecting versions prior to 1.6.3. The vulnerability arises from improper handling of password reset tokens, which are embedded in hidden HTML input fields on the password reset page. This design flaw allows any unauthenticated attacker to obtain a valid password reset token simply by submitting a user's email address to the reset functionality. Since the token is exposed client-side, the attacker can retrieve it without needing to intercept email communications or authenticate as the user. Possession of the reset token enables the attacker to reset the victim’s password and gain full control over the account, resulting in a complete account takeover (ATO). The vulnerability is categorized under CWE-200 (Exposure of Sensitive Information) due to the leakage of sensitive tokens, and CWE-640 (Weak Password Recovery Mechanism) because the password reset process lacks proper security controls. The CVSS v3.0 score of 9.8 reflects the vulnerability’s critical nature, with network attack vector, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild yet, the simplicity of exploitation and the severity of impact make this a high-risk issue. The vendor addressed the vulnerability in Known version 1.6.3 by removing the exposure of the reset token in the HTML and presumably implementing secure token handling practices. Organizations running affected versions should prioritize upgrading to 1.6.3 or later to prevent exploitation.

Potential Impact

The impact of CVE-2026-26273 is severe for organizations using the Known platform, as it allows attackers to perform full account takeovers without requiring access to the victim’s email or any authentication. This can lead to unauthorized access to sensitive user data, manipulation or deletion of published content, impersonation of users, and potential lateral movement within the organization’s infrastructure if accounts have elevated privileges. The compromise of user accounts can damage organizational reputation, result in data breaches, and cause operational disruptions. Since Known is a social publishing platform, attackers could also use compromised accounts to spread misinformation or malicious content. The ease of exploitation and the critical nature of the vulnerability make it a significant threat to confidentiality, integrity, and availability of affected systems and data.

Mitigation Recommendations

To mitigate CVE-2026-26273, organizations should immediately upgrade Known installations to version 1.6.3 or later, where the vulnerability is patched. Beyond upgrading, administrators should audit password reset workflows to ensure sensitive tokens are never exposed client-side or in any user-accessible content. Implement server-side validation and token handling that requires authentication or additional verification steps before allowing password resets. Employ rate limiting and monitoring on password reset endpoints to detect and block mass enumeration attempts. Consider implementing multi-factor authentication (MFA) to reduce the impact of account takeovers. Regularly review and update security controls around authentication and password recovery mechanisms. Finally, educate users about suspicious activity and encourage strong, unique passwords to further reduce risk.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-12T17:10:53.413Z
Cvss Version
3.0
State
PUBLISHED

Threat ID: 698f9fdcc9e1ff5ad86c396f

Added to database: 2/13/2026, 10:04:12 PM

Last enriched: 2/20/2026, 10:32:28 PM

Last updated: 3/30/2026, 4:10:02 PM

Views: 264

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses