CyberCVE

CVE-2025-61624

An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2 all versions,

Severity
Medium 5.4
CVSS 3.1
Adjacent, local or physical access what this means
Exploited
Not listed
EPSS
0.005
40.6th percentile
Discovered by
Vendor
Vendor advisory field
Published
Apr 14, 2026
Assigned by fortinet

Description

An Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') [CWE-22] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4.0 through 7.4.9, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiPAM 1.7.0, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4.0 through 7.4.11, FortiProxy 7.2 all versions, FortiProxy 7.0 all versions, FortiSwitchManager 7.2.0 through 7.2.7, FortiSwitchManager 7.0.0 through 7.0.6 may allow an authenticated attacker with admin profile and at least read-write permissions to write or delete arbitrary files via specific CLI commands.

Weakness: CWE-22

Affected products

Vendor Product Category Matched by
Fortinet FortiOS Check your version Firewall / NGFW cna-assigner
Fortinet FortiPAM Identity / IAM / MFA cna-assigner
Fortinet FortiProxy Check your version SASE / SSE / Secure Web cna-assigner
Fortinet FortiSwitch Routing & Switching cna-assigner
Vendor-reported products (5)
  • Fortinet · FortiOS
  • Fortinet · FortiProxy
  • Fortinet · FortiSwitchManager
  • Fortinet · FortiPAM
  • Siemens · RUGGEDCOM APE1808

Credit

Internal

Vendor remediation

Upgrade to upcoming FortiOS version 8.0.0 or above Upgrade to FortiOS version 7.6.5 or above Upgrade to FortiOS version 7.4.10 or above Upgrade to FortiProxy version 7.6.5 or above Upgrade to FortiProxy version 7.4.12 or above Upgrade to FortiPAM version 1.8.0 or above Upgrade to FortiPAM version 1.7.1 or above Fortinet remediated this issue in FortiSASE version 25.4.b and hence customers do not need to perform any action. Upgrade to upcoming FortiSwitch version 8.0.0 or above Upgrade to FortiSwitch version 7.6.5 or above Upgrade to FortiSwitch version 7.4.9 or above Upgrade to FortiSwitchManager version 7.2.8 or above Upgrade to FortiSwitchManager version 7.0.7 or above

References

Something wrong here?