{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68948 exists.","fix":"No fix has been published for CVE-2025-68948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68948 is a medium-severity vulnerability in B3log Siyuan, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68948 and fix it if it is affected.\n\nWhat it is: CVE-2025-68948 is a medium-severity vulnerability in B3log Siyuan, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68948 exists.\n\nAffected product: B3log Siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-68948/ (Markdown: https://insights.sbomify.com/CVE-2025-68948/index.md)","id":"CVE-2025-68948","markdown":"https://insights.sbomify.com/CVE-2025-68948/index.md","name":"CVE-2025-68948","record":{"aliases":["GHSA-f7ph-rc3w-qp28"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SiYuan knowledge management","requires_auth":"none","summary":"Attackers can decrypt session cookies using a hardcoded secret to steal authentication codes and take over user accounts in SiYuan.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"siyuan","vendor":"b3log"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"SiYuan is self-hosted, open source personal knowledge management software. In versions 3.5.1 and prior, the SiYuan Note application utilizes a hardcoded cryptographic secret for its session store. This unsafe practice renders the session encryption ineffective. Since the sensitive AccessAuthCode is stored within the session cookie, an attacker who intercepts or obtains a user's encrypted session cookie (e.g., via session hijacking) can locally decrypt it using the public key. Once decrypted, the attacker can retrieve the AccessAuthCode in plain text and use it to authenticate or take over the session.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SiYuan: Information Disclosure and Authentication Bypass via Hardcoded Session Secret","id":"CVE-2025-68948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"b3log:siyuan","products":["b3log:siyuan"],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"n8n has a Webhook Node IP Whitelist Bypass via Partial String Matching","id":"CVE-2025-68949"},"packages":[],"prev":{"headline":"NSecsoft NSecKrnl process termination privilege escalation","id":"CVE-2025-68947"},"products":["siyuan"],"published":"2025-12-27","related":[{"cvss_score":9.9,"headline":"SiYuan has an Arbitrary File Read in its Desktop Publish Service","id":"CVE-2026-32938","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":9.8,"headline":"SiYuan has Arbitrary Document Reading within the Publishing Service","id":"CVE-2026-33669","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":9.8,"headline":"SiYuan has directory traversal within its publishing service","id":"CVE-2026-33670","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":9.8,"headline":"SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API","id":"CVE-2026-32767","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-53504","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-53505","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-53506","kev_date_added":null,"published":"2024-11-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["siyuan-note"]},"summary":"Attackers can decrypt session cookies using a hardcoded secret to steal authentication codes and take over user accounts in SiYuan.","url":"https://insights.sbomify.com/CVE-2025-68948/"}