CVE-2025-43856
- Source
- https://cve.org/CVERecord?id=CVE-2025-43856
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-43856.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-43856
- Aliases
-
- GHSA-3832-6r8h-9cfm
- Published
- 2025-07-11T17:10:52.423Z
- Modified
- 2026-04-10T05:31:29.631096Z
- Severity
-
- 7.3 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- immich allows account hijacking through oauth2
- Details
-
immich is a high performance self-hosted photo and video management solution. Prior to 1.132.0, immich is vulnerable to account hijacking through oauth2, because the state parameter is not being checked. The oauth2 state parameter is similar to a csrf token, so when the user starts the login flow this unpredictable token is generated and somehow saved in the browser session and passed to the identity provider, which will return the state parameter when redirecting the user back to immich. Before the user is logged in that parameter needs to be verified to make sure the login was actively initiated by the user in this browser session. On it's own, this wouldn't be too bad, but when immich uses the /user-settings page as a redirect_uri, it will automatically link the accounts if the user was already logged in. This means that if someone has an immich instance with a public oauth provider (like google), an attacker can - for example - embed a hidden iframe in a webpage or even just send the victim a forged oauth login url with a code that logs the victim into the attackers oauth account and redirects back to immich and links the accounts. After this, the attacker can log into the victims account using their own oauth credentials. This vulnerability is fixed in 1.132.0.
- Database specific
{ "cwe_ids": [ "CWE-303" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/43xxx/CVE-2025-43856.json", "cna_assigner": "GitHub_M" }- References