dbcve.org
FortiwebApplication · Fortinet

CVE-2025-59669

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 7.6.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability in FortiWeb versions 7.6.0, 7.4, 7.2, and 7.0 involves hard-coded credentials embedded in the firmware that allow an authenticated attacker with shell access to connect to the redis service and read its data. The redis service likely stores session data, cached application state, or other sensitive operational information that could be exposed through this credential reuse.

MitigationApply the vendor-supplied patch or upgrade to a FortiWeb version that removes the hard-coded redis credentials. Additionally, strictly limit shell access to the device to trusted administrators only and monitor for unauthorized redis connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiwebApplication
Affected:>= 7.0.0, < 7.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FortiWeb installed version
    Run 'get system status' or 'fwc -v' via CLI, or check the web UI dashboard for the firmware version
    Affected if Version is 7.0.0 through 7.6.0 (any version >= 7.0.0 and < 7.6.1)
  2. Verify redis service is running
    Run 'diagnose system redis status' or 'ps | grep redis' via FortiWeb CLI shell
    Affected if Redis process is active and listening on a network interface
  3. Confirm shell access is available
    Check if CLI access with executive shell privileges exists via 'execute shell' command or SSH root-level access
    Affected if Shell access is permitted to any administrative account
  4. Inspect for hard-coded redis credentials in firmware
    Examine firmware files or extracted filesystem for embedded credential strings matching redis service, typically in configuration scripts or binary files
    Affected if Hard-coded redis password or key is found in firmware binaries or configuration files

You are affected if your FortiWeb version is 7.0.0 through 7.6.0, the redis service is accessible, and shell access exists on the device, as the hard-coded credentials could allow unauthorized redis data access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.1 or later
Fixed in 7.6.1
Interim mitigation

Apply the vendor-supplied patch or upgrade to a FortiWeb version that removes the hard-coded redis credentials. Additionally, strictly limit shell access to the device to trusted administrators only and monitor for unauthorized redis connections.

Recommended fix High confidence

FortiWeb 7.6.1

  1. 1. Back up the current FortiWeb configuration using the web UI or CLI backup command
  2. 2. Download FortiWeb firmware version 7.6.1 from the Fortinet support portal (fortinet.com/support)
  3. 3. Upload the firmware file through FortiWeb web UI (System > Maintenance > Firmware) or via CLI using the execute system firmware-upgrade command
  4. 4. After reboot, verify the upgrade was successful by checking the firmware version in the web UI or with the get system status CLI command
  5. 5. Log in and confirm the redis service credentials have been changed from hard-coded values
Caveat Review FortiWeb 7.6.1 release notes for any configuration or feature changes before upgrading; standard upgrade risks apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59669 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data