dbcve.org
FortiadcApplication · Fortinet

CVE-2023-25607

HIGH · 7.8 CVSS v3.1 Published 2023-10-10
Fix available
A fix is available. Upgrade to after 7.0.7 or later.
See remediation →
80/100
Remediation priority · High
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 neutralization of special elements used in an OS Command ('OS Command Injection') vulnerability [CWE-78 ] in FortiManager 7.2.0 through 7.2.2, 7.0.0 through 7.0.7, 6.4.0 through 6.4.11, 6.2 all versions, 6.0 all versions, FortiAnalyzer 7.2.0 through 7.2.2, 7.0.0 through 7.0.7, 6.4.0 through 6.4.11, 6.2 all versions, 6.0 all versions and FortiADC  7.1.0, 7.0.0 through 7.0.3, 6.2 all versions, 6.1 all versions, 6.0 all versions management interface may allow an authenticated attacker with at least READ permissions on system settings to execute arbitrary commands on the underlying shell due to an unsafe usage of the wordexp function.

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

OS command injection vulnerability in FortiManager, FortiAnalyzer, and FortiADC management interfaces allows authenticated attackers with at least READ permissions on system settings to execute arbitrary commands on the underlying shell due to unsafe usage of the wordexp function.

MitigationApply vendor-supplied patches by upgrading to fixed versions (FortiManager 7.2.3+, 7.0.8+, 6.4.12+; FortiAnalyzer 7.2.3+, 7.0.8+, 6.4.12+; FortiADC 7.2.0+, 7.0.4+, 6.3.0+) and restrict management interface access to trusted admin networks.

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
FortiadcApplication
Affected:>= 6.0.0, <= 6.0.4>= 6.1.0, <= 6.1.6>= 6.2.0, <= 6.2.6>= 7.0.0, <= 7.0.3= 7.1.0
FortianalyzerApplication
Affected:>= 6.0.0, <= 6.0.12>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.7= 7.2.1= 7.2.2
FortimanagerApplication
Affected:>= 6.0.0, <= 6.0.12>= 6.2.0, <= 6.2.12>= 6.4.0, <= 6.4.11>= 7.0.0, <= 7.0.7= 7.2.0= 7.2.1= 7.2.2

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

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Fortinet product
    Log into the management interface and check System > Settings or use the CLI command 'get system status' to identify whether the device is FortiManager, FortiAnalyzer, or FortiADC
    Affected if The product is FortiManager, FortiAnalyzer, or FortiADC
  2. Determine the installed version
    Run 'get system status' in the CLI or check the version displayed in the management interface login page footer
    Affected if The version matches any of these ranges: FortiADC 6.0.0-6.0.4, 6.1.0-6.1.6, 6.2.0-6.2.6, 7.0.0-7.0.3, or 7.1.0; FortiAnalyzer 6.0.0-6.0.12, 6.2.0-6.2.12, 6.4.0-6.4.11, 7.0.0-7.0.7, 7.2.1, or 7.2.2; FortiManager 6.0.0-6.0.12, 6.2.0-6.2.12, 6.4.0-6.4.11, 7.0.0-7.0.7, 7.2.0, 7.2.1, or 7.2.2
  3. Verify management interface accessibility
    Confirm that the web-based management interface (port 443 or HTTP port 80) is reachable from network locations outside the trusted admin segment
    Affected if The management interface is exposed to untrusted networks or the internet
  4. Check for user accounts with READ permissions
    In the management interface, navigate to System > Administrators or use CLI 'get admin user' to list accounts. Verify if any accounts have at least READ access to system settings
    Affected if There exist user accounts with READ or higher permissions on system settings, making them potential attackers for this vulnerability

You are affected if you run any of the affected FortiManager, FortiAnalyzer, or FortiADC versions listed and have the management interface accessible to users with READ permissions on system settings.

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 a release after 7.0.7
Interim mitigation

Apply vendor-supplied patches by upgrading to fixed versions (FortiManager 7.2.3+, 7.0.8+, 6.4.12+; FortiAnalyzer 7.2.3+, 7.0.8+, 6.4.12+; FortiADC 7.2.0+, 7.0.4+, 6.3.0+) and restrict management interface access to trusted admin networks.

Recommended fix High confidence

FortiManager: 7.2.3+, 7.0.8+, 6.4.12+, 6.2.13+, 6.0.13+ | FortiAnalyzer: 7.2.3+, 7.0.8+, 6.4.12+, 6.2.13+, 6.0.13+ | FortiADC: 7.1.1+, 7.0.4+, 6.2.7+, 6.1.7+, 6.0.5+

  1. 1. Identify the currently installed FortiManager, FortiAnalyzer, or FortiADC version using the web UI (System Settings > Dashboard > System Information) or CLI command `get system status`.
  2. 2. Determine the appropriate upgrade path based on the current version and product type.
  3. 3. For FortiManager: upgrade to version 7.2.3 or later, 7.0.8 or later, 6.4.12 or later, 6.2.13 or later, or 6.0.13 or later.
  4. 4. For FortiAnalyzer: upgrade to version 7.2.3 or later, 7.0.8 or later, 6.4.12 or later, 6.2.13 or later, or 6.0.13 or later.
  5. 5. For FortiADC: upgrade to version 7.1.1 or later, 7.0.4 or later, 6.2.7 or later, 6.1.7 or later, or 6.0.5 or later.
  6. 6. Download the appropriate firmware from the Fortinet Customer Support portal or Fortiguard Center.
  7. 7. Review Fortinet release notes for upgrade prerequisites and compatibility considerations.
  8. 8. Backup the current configuration before upgrading.
Caveat Review Fortinet release notes for breaking changes between versions; test in a non-production environment before deploying to production

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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