# CVE-2025-7079: mao888 bluebell-plus JWT Token jwt.go hard-coded password

> Attackers can exploit a hard-coded JWT secret in bluebell-plus to bypass authentication, requiring high complexity and permissions.

- **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-5f36-8jq3-3xj6

## What is CVE-2025-7079?

CVE-2025-7079 is a medium-severity vulnerability in mao888 bluebell-plus, 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, has been found in mao888 bluebell-plus up to 2.3.0. This issue affects some unknown processing of the file bluebell_backend/pkg/jwt/jwt.go of the component JWT Token Handler. The manipulation of the argument mySecret with the input bluebell-plus leads to use of hard-coded password. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.

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

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

It affects 1 product.


Products: Mao888 Bluebell-Plus.

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

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

## Is CVE-2025-7079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7079 is a medium-severity vulnerability in mao888 bluebell-plus, 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-7079 exists.

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

## Sources

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

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