{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-24973 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-24973 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-24973 is a critical vulnerability in nexryai concorde, published on 11 Feb 2025. 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-2025-24973 and fix it if it is affected.\n\nWhat it is: CVE-2025-24973 is a critical vulnerability in nexryai concorde, published on 11 Feb 2025. 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-2025-24973 in the wild and no public exploit code.\n\nAffected product: nexryai concorde. 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-24973/ (Markdown: https://insights.sbomify.com/CVE-2025-24973/index.md)","id":"CVE-2025-24973","markdown":"https://insights.sbomify.com/CVE-2025-24973/index.md","name":"CVE-2025-24973","record":{"aliases":["GHSA-2369-p2wh-7cc2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Federated microblogging platform","requires_auth":"none","summary":"Attackers can steal authentication tokens from shared devices because logout fails to clear cookies, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Concorde, formerly know as Nexkey, is a fork of the federated microblogging platform Misskey. Prior to version 12.25Q1.1, due to an improper implementation of the logout process, authentication credentials remain in cookies even after a user has explicitly logged out, which may allow an attacker to steal authentication tokens. This could have devastating consequences if a user with admin privileges is (or was) using a shared device. Users who have logged in on a shared device should go to Settings \u003e Security and regenerate their login tokens. Version 12.25Q1.1 fixes the issue. As a workaround, clear cookies and site data in the browser after logging out.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Concorde not removing authentication tokens after logging out","id":"CVE-2025-24973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"DataEase Mysql JDBC Connection Parameters Not Being Verified Leads to Arbitrary File Read Vulnerability","id":"CVE-2025-24974"},"packages":[],"prev":{"headline":"Discourse may bypass user preference when adding users to chat groups","id":"CVE-2025-24972"},"products":["concorde"],"published":"2025-02-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-02-11","vendors":["nexryai"]},"summary":"Attackers can steal authentication tokens from shared devices because logout fails to clear cookies, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2025-24973/"}