# CVE-2025-7080: Done-0 Jank JWT Token jwt_utils.go hard-coded password

> Hardcoded JWT secrets in Done-0 Jank allow attackers to bypass authentication and forge tokens, requiring remote access and high complexity.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-3g9x-jmhv-45cr

## What is CVE-2025-7080?

CVE-2025-7080 is a medium-severity vulnerability in Done-0 Jank, published on 6 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in Done-0 Jank up to 322caebbad10568460364b9667aa62c3080bfc17. Affected is an unknown function of the file internal/utils/jwt_utils.go of the component JWT Token Handler. The manipulation of the argument accessSecret/refreshSecret with the input jank-blog-secret/jank-blog-refresh-secret leads to use of hard-coded password. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-259 (Use of Hard-coded Password), CWE-255

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


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

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

## Is CVE-2025-7080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7080 is a medium-severity vulnerability in Done-0 Jank, published on 6 Jul 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-7080 exists.

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

## Sources

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

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