Technical impact
The vulnerability exists in ByteStash versions 1.5.0 up through 1.6.0, where the OIDC callback endpoint does not tie the OIDC state parameter to the browser session that initiated the authentication request. This oversight allows an attacker to initiate an OAuth/OpenID Connect login using their own account, then trick a victim into visiting the callback URL generated for that login. When the victim's browser processes the callback, the application accepts it as a legitimate authentication response and logs the victim into the attacker's account. Once logged in, the victim's session is effectively hijacked, granting the attacker access to the victim's personal snippets and any other data available in the victim’s account. The primary impact is unauthorized access to user data via cross‑site request forgery; the severity score reflects a low risk of exploitation under normal circumstances.
Affected Systems
The affected software is ByteStash, a self‑hosted code snippet manager developed by jordan-dalby. Vulnerable releases include all 1.5.x versions and the 1.6.0 release. Version 1.6.1 and later contain the fix that binds OIDC state to the initiating browser session.
Risk and Exploitability
The CVSS score of 2.3 indicates low severity, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is not available, but the nature of the flaw—forcing a victim to visit a crafted callback URL—means exploitation requires social engineering or a malicious link. Because the OIDC state is not bound to the initiating browser session, an attacker can hijack a victim’s session only when the victim follows the link, so the immediate risk is moderate to low until active exploitation is observed. Nonetheless, organizations deploying ByteStash should address the issue promptly, especially if external OIDC providers are enabled.