dbcve.org
FortiosOperating system · Fortinet

CVE-2025-47294

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-28
Fix available
A fix is available. Upgrade to 7.0.15 / 7.2.8 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 integer overflow or wraparound in Fortinet FortiOS versions 7.2.0 through 7.2.7, versions 7.0.0 through 7.0.14 may allow a remote unauthenticated attacker to crash the csfd daemon via a specially crafted request.

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

An integer overflow vulnerability in FortiOS versions 7.0.0-7.0.14 and 7.2.0-7.2.7 allows remote unauthenticated attackers to crash the csfd (Central Synchronization Framework daemon) via specially crafted HTTP/HTTPS requests. The integer wraparound occurs during request processing, leading to memory corruption and daemon crash.

MitigationUpgrade to FortiOS 7.0.15 or 7.2.8 or later to remediate. Until patching is feasible, restrict administrative interface exposure to trusted networks or implement rate limiting on management ports as a compensating control.

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
FortiosOperating system
Affected:>= 6.4.0, < 7.0.15>= 7.2.0, < 7.2.8

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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. Determine FortiOS version
    Run 'get system status' in FortiOS CLI or check Dashboard > Status in the web UI to retrieve the firmware version
    Affected if Version is 7.0.0 through 7.0.14, or 7.2.0 through 7.2.7 (or matches the ranges >= 6.4.0 and < 7.0.15, or >= 7.2.0 and < 7.2.8)
  2. Verify csfd daemon is running
    Run 'diagnose system process list' in CLI and search for the csfd process, or use 'diagnose test application csfd 1' to check daemon status
    Affected if The csfd (Central Synchronization Framework daemon) process is running on the device
  3. Check management interface exposure
    Run 'get system interface' to list interfaces, then review which have 'set management-mode' or HTTP/HTTPS admin access enabled; verify access lists with 'get firewall addrgrp' or 'config system interface' for trusted host restrictions
    Affected if Administrative HTTP/HTTPS access is enabled on interfaces reachable from untrusted networks (not limited to trusted IPs or VPN only)

You are affected if your FortiOS version falls within the vulnerable ranges AND the csfd daemon is active AND your management interface accepts HTTP/HTTPS requests from untrusted networks.

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.0.15 / 7.2.8 or later
Fixed in 7.0.157.2.8
Interim mitigation

Upgrade to FortiOS 7.0.15 or 7.2.8 or later to remediate. Until patching is feasible, restrict administrative interface exposure to trusted networks or implement rate limiting on management ports as a compensating control.

Recommended fix High confidence

FortiOS 7.0.15 or 7.2.8 (depending on current major version branch)

  1. 1. Verify current FortiOS version by running 'get system status' or checking FortiOS web UI dashboard
  2. 2. Download the appropriate firmware upgrade from Fortinet Customer Support portal or FortiGuard
  3. 3. For FortiOS 7.0.x deployments: upgrade to version 7.0.15 or later
  4. 4. For FortiOS 7.2.x deployments: upgrade to version 7.2.8 or later
  5. 5. Upload the firmware via FortiOS CLI using 'execute system firmware upgrade <image>' or via web UI under System > Firmware
  6. 6. After upgrade, verify the csfd daemon is running with 'diagnose system csf status' and confirm the system is stable
  7. 7. Review FortiOS release notes for version 7.0.15 and 7.2.8 for any additional post-upgrade steps or注意事项
Caveat Review FortiOS upgrade path and compatibility notes; ensure all security profiles and configurations are backed up before upgrading

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47294 — 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-47294 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