dbcve.org
FortiwebApplication · Fortinet

CVE-2023-25610

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-24
Fix available
A fix is available. Upgrade to 6.0.12 / 6.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 buffer underwrite ('buffer underflow') vulnerability in the administrative interface of Fortinet FortiOS version 7.2.0 through 7.2.3, version 7.0.0 through 7.0.6, version 6.4.0 through 6.4.11 and version 6.2.12 and below, FortiProxy version 7.2.0 through 7.2.2, version 7.0.0 through 7.0.8, version 2.0.12 and below and FortiOS-6K7K version 7.0.5, version 6.4.0 through 6.4.10 and version 6.2.0 through 6.2.10 and below allows a remote unauthenticated attacker to execute arbitrary code or commands via specifically crafted requests.

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

A buffer underwrite (underflow) vulnerability exists in the administrative interface of FortiOS and FortiProxy that allows a remote unauthenticated attacker to execute arbitrary code via specially crafted requests. The buffer underflow occurs when the software writes data before the start of the allocated memory buffer, potentially allowing memory corruption and arbitrary code execution.

MitigationApply Fortinet's available patches by upgrading FortiOS to version 7.2.4 or later (7.0.7+, 6.4.12+), FortiProxy to 7.2.3/7.0.9 or later, and FortiOS-6K7K to 7.0.6/6.4.11/6.2.11 or later. If immediate patching is not possible, restrict administrative interface access to trusted networks or VPN-only access.

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
FortiwebApplication
Affected:>= 6.1.0, < 6.1.4>= 6.2.0, < 6.2.8>= 6.3.0, < 6.3.23>= 6.4.0, < 6.4.3>= 7.0.0, < 7.0.7>= 7.2.0, < 7.2.2
FortiswitchmanagerApplication
Affected:>= 7.0.0, < 7.0.2>= 7.2.0, < 7.2.2
FortiswitchOperating system
Affected:>= 7.0.0, < 7.0.7>= 7.2.0, < 7.2.4
FortiproxyApplication
Affected:>= 1.1.0, < 7.0.9>= 7.2.0, < 7.2.3
Fortios 6k7kApplication
Affected:>= 6.0.4, < 6.2.13>= 6.4.2, < 6.4.12= 7.0.5
FortiosOperating system
Affected:>= 5.0.0, < 6.2.13>= 6.4.0, < 6.4.12>= 7.0.0, < 7.0.10>= 7.2.0, < 7.2.4
FortimanagerApplication
Affected:>= 6.0.0, < 6.0.12>= 6.2.0, < 6.2.11>= 6.4.0, < 6.4.12>= 7.0.0, < 7.0.5= 7.2.0
FortianalyzerApplication
Affected:>= 6.0.0, < 6.0.12>= 6.2.0, < 6.2.11>= 6.4.0, < 6.4.12>= 7.0.0, < 7.0.5= 7.2.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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 and version
    Run 'get system status' in the CLI or check System Information in the GUI to identify the exact Fortinet product name and its firmware version number
    Affected if The product is any of FortiOS, FortiProxy, Fortiweb, FortiManager, FortiAnalyzer, FortiSwitch, or FortiSwitchManager and the version is within the affected ranges for that product
  2. Compare FortiOS version against affected ranges
    If the product is FortiOS or FortiOS-6K7K, compare the installed version to: 5.0.0 to <6.2.13, 6.4.0 to <6.4.12, 7.0.0 to <7.0.10, or 7.2.0 to <7.2.4
    Affected if The installed FortiOS version falls within any of these ranges
  3. Compare FortiProxy version against affected ranges
    If the product is FortiProxy, compare the installed version to: 1.1.0 to <7.0.9 or 7.2.0 to <7.2.3
    Affected if The installed FortiProxy version falls within either of these ranges
  4. Compare other Fortinet product versions
    For Fortiweb, FortiManager, FortiAnalyzer, FortiSwitch, or FortiSwitchManager, compare the installed version to the specific affected ranges listed for that product in the CVE documentation
    Affected if The installed version for any of these products falls within their respective affected ranges

If any Fortinet product listed in the CVE is running and its version falls within the affected ranges for that product, the environment is affected by this vulnerability.

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 6.0.12 / 6.1.4 / 6.2.8 or later
Fixed in 6.0.126.1.46.2.8
Interim mitigation

Apply Fortinet's available patches by upgrading FortiOS to version 7.2.4 or later (7.0.7+, 6.4.12+), FortiProxy to 7.2.3/7.0.9 or later, and FortiOS-6K7K to 7.0.6/6.4.11/6.2.11 or later. If immediate patching is not possible, restrict administrative interface access to trusted networks or VPN-only access.

Recommended fix High confidence

FortiOS: 6.2.13, 6.4.12, 7.0.10, or 7.2.4 | FortiProxy: 7.0.9 or 7.2.3 | FortiWeb: 6.1.4, 6.2.8, 6.3.23, or 6.4.3 | FortiManager/FortiAnalyzer: 6.0.12, 6.2.11, 6.4.12, or 7.0.5 | FortiSwitch: 7.0.7 or 7.2.4 | FortiSwitchManager: 7.0.2 or 7.2.2

  1. 1. Identify the specific Fortinet product (FortiOS, FortiProxy, FortiWeb, FortiManager, FortiAnalyzer, FortiSwitch, or FortiSwitchManager) and current version from the affected list.
  2. 2. Access the Fortinet support portal at https://support.fortinet.com/ to obtain the appropriate firmware upgrade.
  3. 3. Download the fixed version corresponding to your product: For FortiOS, upgrade to 6.2.13, 6.4.12, 7.0.10, or 7.2.4 or later. For FortiProxy, upgrade to 7.0.9, 7.2.3 or later. For FortiWeb, upgrade to 6.1.4, 6.2.8, 6.3.23, or 6.4.3 or later. For FortiManager/FortiAnalyzer, upgrade to 6.0.12, 6.2.11, 6.4.12, or 7.0.5 or later. For FortiSwitch, upgrade to 7.0.7 or 7.2.4 or later. For FortiSwitchMa
  4. 4. Review the Fortinet release notes for the target version to understand any configuration changes or migration requirements.
  5. 5. Back up the current configuration before upgrading.
  6. 6. Upload and install the new firmware via the administrative interface or CLI.
  7. 7. After upgrade, verify the version and test that administrative interface functionality is working correctly.
Caveat Major version upgrades may require configuration migration review; test in non-production environment first

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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