FortimanagerApplication · Fortinet
CVE-2025-48418
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 · uneditedA hidden functionality vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.3, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2.0 through 7.2.10, FortiAnalyzer 7.0.0 through 7.0.14, FortiAnalyzer 6.4 all versions, FortiAnalyzer Cloud 7.6.2, FortiAnalyzer Cloud 7.4.1 through 7.4.7, FortiAnalyzer Cloud 7.2.1 through 7.2.10, FortiAnalyzer Cloud 7.0.1 through 7.0.14, FortiAnalyzer Cloud 6.4 all versions, FortiManager 7.6.0 through 7.6.3, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2.0 through 7.2.10, FortiManager 7.0.0 through 7.0.14, FortiManager 6.4 all versions, FortiManager Cloud 7.6.2 through 7.6.3, FortiManager Cloud 7.4.1 through 7.4.7, FortiManager Cloud 7.2.1 through 7.2.10, FortiManager Cloud 7.0.1 through 7.0.14, FortiManager Cloud 6.4 all versions may allow a remote authenticated read-only admin with CLI access to escalate their privilege via use of a hidden command.
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 confidenceA hidden functionality vulnerability in Fortinet FortiAnalyzer and FortiManager allows a remote authenticated read-only administrator with CLI access to escalate privileges by executing a hidden command not intended for their privilege level.
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
FortimanagerApplication
>= 6.4.0, < 7.0.15>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.4
Fortimanager CloudApplication
>= 6.4.1, < 7.0.15>= 7.2.1, < 7.2.11>= 7.4.1, < 7.4.8>= 7.6.2, < 7.6.4
FortianalyzerApplication
>= 6.4.0, < 7.0.15>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.4
Fortianalyzer CloudApplication
>= 6.4.1, < 7.0.15>= 7.2.1, < 7.2.11>= 7.4.1, < 7.4.8= 7.6.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiAnalyzer or FortiManager product and versionRun `get system status` or `get system info` in the CLI to retrieve the product name and firmware versionAffected if The product is FortiAnalyzer or FortiManager and the version falls within: 6.4.x, 7.0.x (< 7.0.15), 7.2.x (< 7.2.11), 7.4.x (< 7.4.8), 7.6.x (< 7.6.4)
-
Check for read-only administrator accounts with CLI accessRun `get system admin user` and look for users with `accprofile` set to `read-only` or a limited profile, then check if `trusthost` or `remote-auth` allows CLI accessAffected if A read-only administrator account exists and is configured to access the CLI interface (ssh or console)
-
Verify hidden command availabilityAs the read-only admin, attempt to execute the hidden command referenced in the CVE (typically a privileged exec command not exposed in the help or standard command tree)Affected if The hidden command executes successfully without returning a permission denied error, indicating the privilege escalation is possible
You are affected if you run a vulnerable FortiAnalyzer or FortiManager version within the affected ranges AND have read-only administrator accounts with CLI access enabled, as this combination allows privilege escalation via the hidden command.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.157.2.117.4.8
Restrict CLI access for read-only admin accounts and apply vendor patches for the affected versions (7.0.14+, 7.2.10+, 7.4.7+, 7.6.3+).
FortiManager/FortiAnalyzer 7.6.x → 7.6.4; 7.4.x → 7.4.8; 7.2.x → 7.2.11; 7.0.x → 7.0.15; 6.4.x → 7.0.15 or later
- Identify the currently installed FortiManager or FortiAnalyzer version by running `get system status` in the CLI or checking the Web UI dashboard
- For FortiManager: Upgrade to version 7.6.4 or later for 7.6.x installs; upgrade to 7.4.8 or later for 7.4.x installs; upgrade to 7.2.11 or later for 7.2.x installs; upgrade to 7.0.15 or later for 7.0.x installs
- For FortiManager Cloud: Upgrade to version 7.6.4 or later for 7.6.x installs; upgrade to 7.4.8 or later for 7.4.x installs; upgrade to 7.2.11 or later for 7.2.x installs; upgrade to 7.0.15 or later for 7.0.x installs
- For FortiAnalyzer: Upgrade to version 7.6.4 or later for 7.6.x installs; upgrade to 7.4.8 or later for 7.4.x installs; upgrade to 7.2.11 or later for 7.2.x installs; upgrade to 7.0.15 or later for 7.0.x installs
- For FortiAnalyzer Cloud: Upgrade to version 7.6.4 or later for 7.6.x installs; upgrade to 7.4.8 or later for 7.4.x installs; upgrade to 7.2.11 or later for 7.2.x installs; upgrade to 7.0.15 or later for 7.0.x installs
- After upgrade, verify the version by running `get system status` in the CLI
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48418 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48418 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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