dbcve.org
FortirecorderApplication · Fortinet

CVE-2024-47566

MEDIUM · 6.0 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 7.0.5 / 7.2.2 or later.
See remediation →
62/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 improper limitation of a pathname to a restricted directory ('path traversal') [CWE-23] in Fortinet FortiRecorder version 7.2.0 through 7.2.1 and before 7.0.4 allows a privileged attacker to delete files from the underlying filesystem via crafted CLI requests.

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

FortiRecorder contains a path traversal vulnerability (CWE-23) in its CLI interface that allows privileged attackers to craft malicious requests that bypass directory restrictions and delete files outside the intended filesystem boundaries. The vulnerability affects versions 7.2.0 through 7.2.1 and versions before 7.0.4, enabling unauthorized file deletion via specially constructed CLI commands.

MitigationApply vendor-supplied patches by upgrading to FortiRecorder 7.2.2, 7.0.4, or later. Until patches can be deployed, strictly limit CLI access to trusted, least-privilege users and implement monitoring for anomalous CLI request patterns.

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
FortirecorderApplication
Affected:>= 6.4.0, < 7.0.5>= 7.2.0, < 7.2.2

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify FortiRecorder version
    Run 'get system status' in the FortiRecorder CLI or check the GUI dashboard for firmware version information
    Affected if The installed version is 6.4.0 through 7.0.4, or 7.2.0 through 7.2.1 (versions before 7.0.5 and before 7.2.2)
  2. Confirm CLI access is enabled
    Check user accounts with CLI access permissions via 'get system admin' in the CLI or review admin profiles in the GUI under System > Administrators
    Affected if Any administrative or privileged user account has CLI access, as the vulnerability is exploited through the CLI interface

The environment is affected if FortiRecorder version is 6.4.0-7.0.4 or 7.2.0-7.2.1 and the CLI interface is accessible to privileged users.

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.5 / 7.2.2 or later
Fixed in 7.0.57.2.2
Interim mitigation

Apply vendor-supplied patches by upgrading to FortiRecorder 7.2.2, 7.0.4, or later. Until patches can be deployed, strictly limit CLI access to trusted, least-privilege users and implement monitoring for anomalous CLI request patterns.

Recommended fix High confidence

FortiRecorder 7.0.5+ (for 6.4.0-7.0.4) or 7.2.2+ (for 7.2.0-7.2.1)

  1. 1. Identify the currently installed FortiRecorder version using the CLI command: get system status
  2. 2. If running version 6.4.0 through 7.0.4, plan upgrade to version 7.0.5 or later in the 7.0.x branch
  3. 3. If running version 7.2.0 through 7.2.1, plan upgrade to version 7.2.2 or later in the 7.2.x branch
  4. 4. Review Fortinet release notes for upgrade procedures and prerequisites
  5. 5. Back up current FortiRecorder configuration before upgrading
  6. 6. Download the appropriate firmware from Fortinet support portal or FortiGuard
  7. 7. Upload and install the firmware via FortiRecorder web UI or CLI: execute upgrade firmware
  8. 8. After upgrade, verify the new version is installed: get system status
Caveat Review Fortinet release notes for any configuration or feature changes between versions; minor version upgrades within same branch typically maintain compatibility

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

Fix this in Fortirecorder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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