# CVE-2025-59669: Hardcoded credentials in FortiWeb

> An authenticated attacker with shell access can use hard-coded credentials to connect to the Redis service and access its data.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:U/RC:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-r5ph-gxvr-rv3j

## What is CVE-2025-59669?

CVE-2025-59669 is a medium-severity vulnerability in Fortinet Fortiweb, published on 18 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A use of hard-coded credentials vulnerability in Fortinet FortiWeb 7.6.0, FortiWeb 7.4 all versions, FortiWeb 7.2 all versions, FortiWeb 7.0 all versions may allow an authenticated attacker with shell access to the device to connect to redis service and access its data

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Fortinet Fortiweb.

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

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

## Is CVE-2025-59669 being exploited?

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

## Other vulnerabilities in Fortinet Fortiweb

- [CVE-2025-25257](https://insights.sbomify.com/CVE-2025-25257/): Fortinet FortiWeb SQL Injection (critical 9.6, exploited in the wild)
- [CVE-2025-64446](https://insights.sbomify.com/CVE-2025-64446/): Fortinet FortiWeb Path Traversal (critical 9.4, exploited in the wild)
- [CVE-2025-58034](https://insights.sbomify.com/CVE-2025-58034/): Fortinet FortiWeb OS Command Injection (medium 6.7, exploited in the wild)
- [CVE-2020-29015](https://insights.sbomify.com/CVE-2020-29015/): SQL injection in Fortinet FortiWeb (critical 9.8)
- [CVE-2020-29016](https://insights.sbomify.com/CVE-2020-29016/): Memory corruption in Fortinet FortiWeb (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59669 is a medium-severity vulnerability in Fortinet Fortiweb, published on 18 Nov 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-59669 in the wild and no public exploit code.

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

## Sources

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

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