# CVE-2025-24973: Concorde not removing authentication tokens after logging out

> Attackers can steal authentication tokens from shared devices because logout fails to clear cookies, potentially leading to account takeover.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2025
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-2369-p2wh-7cc2

## What is CVE-2025-24973?

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.

### Official 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 > 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-24973?


## How do I fix CVE-2025-24973?

No fix has been published for CVE-2025-24973 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24973 being exploited?

There is no known exploitation of CVE-2025-24973 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24973 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2025-24973 in the wild and no public exploit code.

Affected product: nexryai concorde. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24973/ (Markdown: https://insights.sbomify.com/CVE-2025-24973/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24973
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24973
- OSV: https://osv.dev/vulnerability/CVE-2025-24973

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24973/
Summaries are generated and may contain mistakes; the official description above is the record.