29 matches found
CVE-2026-134799
The ByteStash application (version 1.5.0 before 1.6.1) is vulnerable to a Login CSRF flaw in the /api/auth/oidc/callback handler. The root cause is that OIDC state is not properly bound to the initiating browser. An attacker can initiate an OIDC login with their own account and trick a victim int...
CVE-2026-134279 Vikunja from 0.20.5 before 2.8.0 Login CSRF via OIDC Callback State Check
Vikunja from 0.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log...
CVE-2026-134279
Vikunja versions from 0.20.5 before 2.8.0 are vulnerable to a Login CSRF vulnerability within the OpenID Connect callback functionality. The flaw exists in the OpenIdAuth.vue component, which accepts a valueless state parameter. An attacker can provide a crafted callback link containing an empty ...
CVE-2026-123495
Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-site request forgery. An attacker with an account can lure a victim to a page posting the attacker's credentials or OIDC code, switching the...
EUVD-2026-119380
Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-site request forgery. An attacker with an account can lure a victim to a page posting the attacker's credentials or OIDC code, switching the...
CVE-2026-123495
Vikunja versions 2.0.0 before 2.7.1 are vulnerable to Login CSRF due to a lack of CSRF or Origin checks on the /api/v2 login and OIDC callback endpoints. An attacker with an account can trick a victim into visiting a malicious page that submits the attacker's credentials or OIDC code. This action...
CVE-2026-123495 Vikunja 2.0.0 before 2.7.1 Login CSRF via /api/v2 Login and OIDC Callback
Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-site request forgery. An attacker with an account can lure a victim to a page posting the attacker's credentials or OIDC code, switching the...
CVE-2026-123495 Vikunja 2.0.0 before 2.7.1 Login CSRF via /api/v2 Login and OIDC Callback
Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-site request forgery. An attacker with an account can lure a victim to a page posting the attacker's credentials or OIDC code, switching the...
PT-2026-139776
Name of the Vulnerable Software and Affected Versions Vikunja versions 2.0.0 through 2.7.0 Description The software accepts form-encoded bodies on the '/api/v2' login and OIDC callback endpoints without implementing Cross-Site Request Forgery CSRF or Origin checks. This allows an attacker to...
CVE-2026-123495: go-vikunja vikunja: Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF orβ¦
Vikunja 2.0.0 before 2.7.1 accepts form-encoded bodies on the /api/v2 login and OIDC callback endpoints without CSRF or Origin checks, enabling login cross-site request forgery. An attacker with an account can lure a victim to a page posting the attacker's credentials or OIDC code, switching the...
CVE-2026-61640 Wallos: SSRF via OIDC Token/UserInfo URL Configuration
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, Admin-configured OIDC tokenurl and userinfourl in includes/oidc/handleoidccallback.php:18-49 are used directly in curlinit with zero SSRF filtering. Unlike logo/webhook URLs which have...
EUVD-2026-68810
Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, Admin-configured OIDC tokenurl and userinfourl in includes/oidc/handleoidccallback.php:18-49 are used directly in curlinit with zero SSRF filtering. Unlike logo/webhook URLs which have...
PT-2026-83993
Name of the Vulnerable Software and Affected Versions Wallos versions prior to 4.9.6 Description An issue exists where administrator-configured OpenID Connect OIDC token url and user info url variables within the handle oidc callback.php file are used directly in the curl init function without...
Origin Validation Error
Overview Affected versions of this package are vulnerable to Origin Validation Error in the OIDC callback handling. An attacker can gain unauthorized access by substituting an access token minted for another client, thereby creating authenticated sessions without proper issuer, audience, nonce, o...
CVE-2026-82462
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification...
CVE-2026-82462
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification...
CVE-2026-82462 pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification...
CVE-2026-82462
pac4j-oidc versions prior to 6.5.6 contain an authentication bypass vulnerability in the OIDC callback handling. The OidcCredentialsExtractor accepts callbacks carrying only an access token without requiring an authorization code or ID token, allowing attackers to substitute access tokens minted ...
EUVD-2026-68119
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification...
PT-2026-83442
pac4j-oidc before 6.5.6 accepts OIDC callbacks carrying only an access token without authorization code or ID token validation. Attackers can substitute access tokens minted for other clients to create authenticated sessions without proper issuer, audience, nonce, or subject verification...