dbcve.org
FortiproxyApplication · Fortinet

CVE-2025-54821

MEDIUM · 6.0 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 1.6.1 / 7.6.4 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
An Improper Privilege Management vulnerability [CWE-269] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiOS 7.4.0 through 7.4.11, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions, FortiPAM 1.6.0, 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, FortiSASE 25.2.91 may allow an authenticated administrator to bypass the trusted host policy via crafted CLI 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 confidence

This is an Improper Privilege Management (CWE-269) vulnerability in multiple Fortinet products where an authenticated administrator can bypass the trusted host policy via a crafted CLI command. The trusted host policy typically restricts administrative access to specific IP addresses, but this vulnerability allows a legitimate admin to circumvent that control.

MitigationApply the vendor-supplied patch or upgrade to a fixed FortiOS/FortiPAM/FortiSASE version. Review trusted host policy configurations and monitor for unauthorized administrative access attempts from unexpected source IPs.

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
FortiproxyApplication
Affected:>= 7.0.0, < 7.6.4
FortipamOperating system
Affected:>= 1.0.0, < 1.6.1
FortiosOperating system
Affected:>= 6.4.0, < 7.6.4

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
High
Integrity
High
Availability
None

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

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 the Fortinet product and version
    Run the command to display system information, such as 'get system status' or ' diagnose hardware sysinfo' via CLI, or check the web UI dashboard for the firmware version
    Affected if The product is FortiOS version >= 6.4.0 and < 7.6.4, FortiPAM version >= 1.0.0 and < 1.6.1, or FortiProxy version >= 7.0.0 and < 7.6.4
  2. Check if trusted host policy is configured
    Review the administrative user configuration by running 'show system admin' or checking the trusted hosts/ trusted host policy settings in the CLI configuration
    Affected if Any trusted host IP restrictions are defined for administrative accounts, indicating the trusted host feature is in use
  3. Verify the administrative access methods in use
    Examine the system interface configuration for administrative access settings, using 'show system interface' or reviewing the web UI under System > Network > Interface
    Affected if Administrative access (HTTP/HTTPS/SSH/CLI) is enabled on interfaces accessible from networks other than the defined trusted host ranges
  4. Review recent administrative login sources
    Check authentication logs and audit trails for administrative logins, using 'execute log filter category 1' and reviewing event logs for admin login events
    Affected if Administrative logins originate from IP addresses outside the configured trusted host ranges

You are affected if you are running a vulnerable version (FortiOS 6.4.0-7.6.3, FortiPAM 1.0.0-1.6.0, or FortiProxy 7.0.0-7.6.3) AND have trusted host policies configured that restrict admin access to specific IP addresses.

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 1.6.1 / 7.6.4 or later
Fixed in 1.6.17.6.4
Interim mitigation

Apply the vendor-supplied patch or upgrade to a fixed FortiOS/FortiPAM/FortiSASE version. Review trusted host policy configurations and monitor for unauthorized administrative access attempts from unexpected source IPs.

Recommended fix High confidence

FortiOS 7.6.4+ | FortiPAM 1.6.1+ | FortiProxy 7.6.4+

  1. 1. Identify the affected Fortinet product (FortiOS, FortiPAM, or FortiProxy) in your environment.
  2. 2. Determine the current installed version using the CLI command: `get system status` or `get system version`.
  3. 3. For FortiOS: Upgrade to version 7.6.4 or later (if running 6.4.x, 7.0.x, 7.2.x, 7.4.x, or 7.6.0-7.6.3).
  4. 4. For FortiPAM: Upgrade to version 1.6.1 or later (if running 1.0.x through 1.6.0).
  5. 5. For FortiProxy: Upgrade to version 7.6.4 or later (if running 7.0.0 through 7.6.3).
  6. 6. Download the firmware from Fortinet's support portal: https://support.fortinet.com/
  7. 7. Upload the firmware via FortiOS/FortiPAM/FortiProxy GUI or CLI: `execute upgrade firmware <image-file>`
  8. 8. After upgrade, verify the trusted host policy is working correctly by testing access from non-trusted IPs.
Caveat Review Fortinet release notes for 7.6.4/1.6.1 for any configuration changes or deprecated features before upgrading

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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