An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 7.6.0 through…
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2.0 through 7.2.11, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2.0 through 7.2.11, FortiManager Cloud 7.6.0 through 7.6.4, FortiManager Cloud 7.4.1 through 7.4.7, FortiManager Cloud 7.2.1 through 7.2.10 may allow an authenticated attacker whose profile only has read permission to write and delete files from the underlying filesystem via crafted HTTP or HTTPs requests.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 49 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-61625 (An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiAnalyzer 7.6.0 through…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-61625 (entry last updated 2026-11-10):
Affected:
- Fortinet FortiManager: from 7.6.0, through 7.6.4; from 7.4.0, through 7.4.7; from 7.2.0, through 7.2.11
- Fortinet FortiAnalyzer: from 7.6.0, through 7.6.4; from 7.4.0, through 7.4.7; from 7.2.0, through 7.2.11
- Fortinet FortiManager Cloud: from 7.6.0, through 7.6.4; from 7.4.1, through 7.4.7; from 7.2.1, through 7.2.10
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2025-61625 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-61625 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-190
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-61625
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2025-61625.Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Fortinet FortiManager
From 7.6.0 · through 7.6.4; From 7.4.0 · through 7.4.7; From 7.2.0 · through 7.2.11
- Fortinet FortiAnalyzer
From 7.6.0 · through 7.6.4; From 7.4.0 · through 7.4.7; From 7.2.0 · through 7.2.11
- Fortinet FortiManager Cloud
From 7.6.0 · through 7.6.4; From 7.4.1 · through 7.4.7; From 7.2.1 · through 7.2.10
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-61625
Is CVE-2025-61625 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2025-61625?
FortiManager: from 7.6.0 through 7.6.4; from 7.4.0 through 7.4.7; from 7.2.0 through 7.2.11. FortiAnalyzer: from 7.6.0 through 7.6.4; from 7.4.0 through 7.4.7; from 7.2.0 through 7.2.11. FortiManager Cloud: from 7.6.0 through 7.6.4; from 7.4.1 through 7.4.7; from 7.2.1 through 7.2.10.Source: cve.now feed data