dbcve.org
Fortiextender FirmwareOperating system · Fortinet

CVE-2025-46775

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.3 or later.
See remediation →
57/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 debug messages revealing unnecessary information vulnerability in Fortinet FortiExtender 7.6.0 through 7.6.1, FortiExtender 7.4.0 through 7.4.6, FortiExtender 7.2 all versions, FortiExtender 7.0 all versions may allow an authenticated user to obtain administrator credentials via debug log commands.

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 · moderate confidence

FortiExtender contains a debug logging vulnerability where authenticated users can obtain administrator credentials through debug log commands. The debug messages inappropriately expose sensitive credential information that should be redacted or masked in log output.

MitigationUpgrade to a patched FortiExtender version beyond 7.6.1, 7.4.6 or disable debug logging in production until patching is possible. Restrict access to debug commands to only necessary personnel.

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
Fortiextender FirmwareOperating system
Affected:>= 7.0.0, < 7.4.8>= 7.6.0, < 7.6.3

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 FortiExtender firmware version
    Run 'get system status' or access the FortiExtender GUI/CLI to view the firmware version installed
    Affected if Version is >= 7.0.0 and < 7.4.8, or >= 7.6.0 and < 7.6.3
  2. Verify debug logging is accessible
    Check if debug commands are available to authenticated users via CLI using 'diagnose debug' or similar debug command interfaces
    Affected if Debug commands are accessible to non-administrator authenticated users
  3. Inspect debug log output for credential exposure
    Enable debug logging and review log output for any instances where administrator passwords, API keys, or other credentials appear unmasked or in plain text
    Affected if Debug logs contain unmasked or plain-text credential information

A user is affected if their FortiExtender firmware version falls within the listed ranges AND debug logging is enabled and accessible to authenticated users who can trigger credential exposure in log output.

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.4.8 / 7.6.3 or later
Fixed in 7.4.87.6.3
Interim mitigation

Upgrade to a patched FortiExtender version beyond 7.6.1, 7.4.6 or disable debug logging in production until patching is possible. Restrict access to debug commands to only necessary personnel.

Recommended fix High confidence

FortiExtender 7.4.8 or later, or FortiExtender 7.6.3 or later

  1. Identify the current FortiExtender firmware version by accessing the device GUI or CLI
  2. Determine which branch (7.4.x or 7.6.x) is appropriate for your environment and upgrade path
  3. Download the firmware image for FortiExtender 7.4.8 or later from Fortinet's support portal (https://support.fortinet.com)
  4. Upload the firmware image via FortiExtender GUI (System > Firmware) or CLI using the execute upgrade command
  5. Verify the upgrade was successful and confirm the new version in the device GUI or via 'get system status' CLI command
  6. After upgrade, verify the vulnerability is resolved by ensuring debug logs no longer expose credentials
Caveat Review Fortinet release notes for any configuration or behavioral changes between versions before upgrading

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

Fix this in Fortiextender Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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