{"answers":{"affected":"2 open source packages ship an affected version, including @workos-inc/authkit-nextjs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-51752 in the wild and no public exploit code.","fix":"Upgrade @workos-inc/authkit-nextjs to 0.13.2 or later.","what":"CVE-2024-51752 is a low-severity vulnerability in workos authkit-nextjs, published on 5 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-51752 and fix it if it is affected.\n\nWhat it is: CVE-2024-51752 is a low-severity vulnerability in workos authkit-nextjs, published on 5 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-51752 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @workos-inc/authkit-nextjs (npm): affected all versions; fixed in 0.13.2\n- @workos-inc/authkit-nextjs (npm): affected all versions; fixed in 0.13.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-51752/ (Markdown: https://insights.sbomify.com/CVE-2024-51752/index.md)","id":"CVE-2024-51752","markdown":"https://insights.sbomify.com/CVE-2024-51752/index.md","name":"CVE-2024-51752","record":{"aliases":["GHSA-5wmg-9cvh-qw25"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Next.js AuthKit library","requires_auth":"none","summary":"Attackers can obtain refresh tokens if the debug flag is enabled, potentially leading to session hijacking.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"authkit-nextjs","vendor":"workos"}],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The AuthKit library for Next.js provides convenient helpers for authentication and session management using WorkOS \u0026 AuthKit with Next.js. In affected versions refresh tokens are logged to the console when the disabled by default `debug` flag, is enabled. This issue has been patched in version 0.13.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Refresh tokens are logged when the debug flag is enabled in @workos-inc/authkit-nextjs","id":"CVE-2024-51752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Refresh tokens are logged when the debug flag is enabled in @workos-inc/authkit-remix","id":"CVE-2024-51753"},"packages":[{"ecosystem":"npm","fixed":["0.13.2"],"introduced":["0"],"last_affected":[],"package":"@workos-inc/authkit-nextjs","purl":null,"source":"GHSA-5wmg-9cvh-qw25"},{"ecosystem":"npm","fixed":["0.13.2"],"introduced":["0"],"last_affected":[],"package":"@workos-inc/authkit-nextjs","purl":"pkg:npm/%40workos-inc/authkit-nextjs","source":"GHSA-5wmg-9cvh-qw25"}],"prev":{"headline":"Arbitrary file read with File and UploadButton components in Gradio","id":"CVE-2024-51751"},"products":["authkit-nextjs"],"published":"2024-11-05","related":[{"cvss_score":8,"headline":"authkit-nextjs may let session cookies be cached in CDNs","id":"CVE-2025-64762","kev_date_added":null,"published":"2025-11-21"},{"cvss_score":4.8,"headline":"@workos-inc/authkit-nextjs session replay vulnerability","id":"CVE-2024-29901","kev_date_added":null,"published":"2024-03-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-05","vendors":["workos"]},"summary":"Attackers can obtain refresh tokens if the debug flag is enabled, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2024-51752/"}