dbcve.org
FortiwebApplication · Fortinet

CVE-2025-32766

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 7.4.9 / 7.6.4 or later.
See remediation →
69/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 stack-based buffer overflow vulnerability [CWE-121] in Fortinet FortiWeb CLI version 7.6.0 through 7.6.3 and before 7.4.8 allows a privileged attacker to execute arbitrary code or commands via crafted CLI 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 · high confidence

A stack-based buffer overflow vulnerability in FortiWeb CLI versions 7.4.x before 7.4.8 and 7.6.0 through 7.6.3 allows authenticated privileged attackers to execute arbitrary code or commands via specially crafted CLI input due to insufficient bounds checking on the stack.

MitigationUpgrade FortiWeb to version 7.4.8 or later, or 7.6.4 or later to remediate this vulnerability. Alternatively, restrict CLI access to only trusted privileged users and monitor for suspicious CLI activity.

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:>= 7.4.1, < 7.4.9>= 7.6.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
High

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

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

  1. Check FortiWeb firmware version
    Log into the FortiWeb web UI and navigate to System > Firmware, or run 'get system status' via CLI to retrieve the current firmware version
    Affected if The version is 7.4.1 through 7.4.7, or 7.6.0 through 7.6.3 (versions below 7.4.8 or 7.6.4)
  2. Confirm CLI interface is accessible
    Verify that SSH access to FortiWeb CLI is enabled by checking the system interface configuration via 'show system interface' or checking that port 22 is open
    Affected if CLI access (SSH or console) is enabled, which is the default configuration for FortiWeb
  3. Review privileged admin accounts
    Run 'get system admin' via CLI to list all administrative users and their privilege levels
    Affected if There are multiple privileged admin accounts, increasing the attack surface for authenticated exploitation

You are affected if your FortiWeb version is 7.4.1-7.4.7 or 7.6.0-7.6.3 and CLI access is enabled, since the vulnerability allows authenticated privileged attackers to execute code via crafted CLI input.

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.9 / 7.6.4 or later
Fixed in 7.4.97.6.4
Interim mitigation

Upgrade FortiWeb to version 7.4.8 or later, or 7.6.4 or later to remediate this vulnerability. Alternatively, restrict CLI access to only trusted privileged users and monitor for suspicious CLI activity.

Recommended fix High confidence

FortiWeb 7.4.9 or later; FortiWeb 7.6.4 or later

  1. 1. Identify the current FortiWeb version by running `get system status` in the CLI or checking the FortiWeb web UI dashboard.
  2. 2. For FortiWeb versions 7.4.1 through 7.4.8: Plan upgrade to version 7.4.9 or later.
  3. 3. For FortiWeb versions 7.6.0 through 7.6.3: Plan upgrade to version 7.6.4 or later.
  4. 4. Before upgrading, backup the FortiWeb configuration using `execute backup full-config` command.
  5. 5. Download the firmware upgrade from Fortinet's support portal at https://support.fortinet.com/.
  6. 6. Upload the firmware file via the FortiWeb web UI (System > Firmware > Upload) or CLI using `execute restore firmware` command.
  7. 7. After upgrade, verify the new version using `get system status` and confirm the vulnerability is resolved.
Caveat Review FortiWeb release notes for any configuration or feature changes between your current version and the target version before upgrading

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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