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-28678: CWE-311: Missing Encryption of Sensitive Data in toxicbishop DSA-with-tsx

0
High
VulnerabilityCVE-2026-28678cvecve-2026-28678cwe-311cwe-522
Published: Sat Mar 07 2026 (03/07/2026, 16:06:51 UTC)
Source: CVE Database V5
Vendor/Project: toxicbishop
Product: DSA-with-tsx

Description

DSA Study Hub is an interactive educational web application. Prior to commit d527fba, the user authentication system in server/routes/auth.js was found to be vulnerable to Insufficiently Protected Credentials. Authentication tokens (JWTs) were stored in HTTP cookies without cryptographic protection of the payload. This issue has been patched via commit d527fba.

AI-Powered Analysis

AILast updated: 03/07/2026, 16:30:52 UTC

Technical Analysis

CVE-2026-28678 identifies a vulnerability in the toxicbishop DSA-with-tsx product, an interactive educational web application known as DSA Study Hub. The issue lies in the user authentication system implemented in server/routes/auth.js, where JSON Web Tokens (JWTs) used for authentication were stored in HTTP cookies without cryptographic protection of the payload. This means the JWTs were susceptible to interception and tampering during transmission or via client-side attacks such as cross-site scripting (XSS). The vulnerability is classified under CWE-311 (Missing Encryption of Sensitive Data) and CWE-522 (Insufficiently Protected Credentials). The lack of encryption on authentication tokens compromises confidentiality and integrity, allowing attackers to potentially hijack user sessions or impersonate users. The vulnerability was present in all versions prior to commit d527fba, which introduced cryptographic protection for the JWT payload in cookies, effectively mitigating the risk. The CVSS v3.1 score of 8.1 reflects a network attack vector with low complexity, no privileges required, but user interaction needed (e.g., tricking a user to visit a malicious site). The scope is unchanged, but the impact on confidentiality and integrity is high, while availability is unaffected. No known exploits are currently reported in the wild, but the vulnerability poses a significant risk due to the sensitive nature of authentication tokens and the widespread use of JWTs in web applications.

Potential Impact

The primary impact of this vulnerability is the compromise of user authentication tokens, which can lead to unauthorized access to user accounts and sensitive data within the DSA Study Hub application. Attackers who intercept or manipulate JWTs can impersonate legitimate users, potentially gaining access to personal information, educational content, or administrative functions depending on user roles. This undermines user trust and can lead to data breaches, privacy violations, and reputational damage for organizations deploying the affected software. Since the vulnerability requires user interaction but no privileges, phishing or social engineering attacks could facilitate exploitation. The lack of encryption on tokens also increases the risk in environments where network traffic can be monitored or manipulated, such as public Wi-Fi or compromised networks. Although availability is not directly impacted, the integrity and confidentiality breaches can have cascading effects on organizational security posture and compliance with data protection regulations.

Mitigation Recommendations

Organizations using toxicbishop DSA-with-tsx should immediately update to the patched version containing commit d527fba or later, which implements cryptographic protection of JWT payloads in cookies. Beyond patching, it is critical to enforce secure cookie attributes such as Secure, HttpOnly, and SameSite flags to reduce the risk of token theft via client-side attacks. Implementing Content Security Policy (CSP) headers can mitigate cross-site scripting risks that might expose tokens. Additionally, monitoring authentication logs for unusual token usage or session anomalies can help detect exploitation attempts. Employing network-level protections such as TLS encryption for all communications is essential to prevent interception. Educating users about phishing risks and enforcing multi-factor authentication (MFA) can further reduce the impact of compromised tokens. Regular security audits and code reviews focusing on credential storage and transmission practices should be institutionalized to prevent similar vulnerabilities.

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-03-02T21:43:19.927Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69ac4f4bc48b3f10ffae7ab6

Added to database: 3/7/2026, 4:16:11 PM

Last enriched: 3/7/2026, 4:30:52 PM

Last updated: 3/8/2026, 4:11:45 AM

Views: 10

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 in Console -> Billing 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