# CVE-2025-47945: Donetick Has Weak Default JWT Secret

> Donetick uses a weak default JWT secret, allowing attackers to forge tokens and achieve full account takeover of any user.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-hjjg-vw4j-986x

## What is CVE-2025-47945?

CVE-2025-47945 is a critical vulnerability in donetick, published on 17 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Donetick an open-source app for managing tasks and chores. Prior to version 0.1.44, the application uses JSON Web Tokens (JWT) for authentication, but the signing secret has a weak default value. While the responsibility is left to the system administrator to change it, this approach is inadequate. The vulnerability is proven by existence of the issue in the live version as well. This issue can result in full account takeover of any user. Version 0.1.44 contains a patch.

Weakness: CWE-453 (Insecure Default Variable Initialization), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Donetick Donetick.

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

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

## Is CVE-2025-47945 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47945 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47945 is a critical vulnerability in donetick, published on 17 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47945 exists.

Affected product: donetick. 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-47945/ (Markdown: https://insights.sbomify.com/CVE-2025-47945/index.md)
```

## Sources

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

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