Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Hard-coded credentials in Fortinet FortiWeb Redis service

IdentifiersCVE-2025-59669CWE-798· Use of Hard-coded Credentials

CVE-2025-59669 is a use of hard-coded credentials vulnerability affecting Fortinet FortiWeb 7.6.0, 7.4 all versions, 7.2 all versions, and 7.0 all versions. According to the provided content, FortiWeb contains hard-coded credentials associated with its internal Redis service. An authenticated attacker who already has shell access to the device can use those embedded credentials to connect to the Redis service and access stored data. The issue is therefore rooted in the presence of fixed credentials within the product rather than administrator-configured secrets.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker with authenticated shell access on the FortiWeb appliance to authenticate to the internal Redis service and access its data. This can expose sensitive application or operational data stored in Redis and may facilitate further post-exploitation activity depending on what information is present in that datastore. Based on the provided information, the confirmed impact is unauthorized access to Redis data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict shell access to the FortiWeb device to only highly trusted administrators, minimize the number of accounts capable of obtaining shell access, and tightly control administrative pathways to the appliance. Limit access to the internal Redis service through host-based and network segmentation controls where feasible, monitor for unexpected Redis connections or access patterns on the appliance, and review appliance access logs for signs of post-authentication abuse. These are compensating controls only; patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Apply Fortinet updates that remediate CVE-2025-59669 in affected FortiWeb releases. The provided content states that Fortinet has released patches and recommends immediate updates to affected systems. Upgrade from affected versions of FortiWeb 7.6.0, 7.4.x, 7.2.x, and 7.0.x to vendor-fixed releases as identified by Fortinet.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortiwebapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.