dbcve.org
FortiwebApplication · Fortinet

CVE-2025-27759

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 7.0.11 / 7.2.11 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
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] in Fortinet FortiWeb version 7.6.0 through 7.6.3, 7.4.0 through 7.4.7, 7.2.0 through 7.2.10 and before 7.0.10 allows an authenticated privileged attacker to execute unauthorized 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

OS command injection vulnerability in FortiWeb's CLI interface allows authenticated privileged attackers to execute arbitrary OS commands through specially crafted CLI commands, exploiting improper neutralization of special elements in command input.

MitigationApply Fortinet's patches: upgrade to version 7.6.4 or later, 7.4.8 or later, 7.2.11 or later, or 7.0.10 or later. Restrict CLI access to only necessary privileged personnel and monitor for unauthorized command execution.

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.0.0, < 7.0.11>= 7.2.0, < 7.2.11>= 7.4.0, < 7.4.8>= 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 CLI and run the command 'get system status' or access the web UI under Dashboard > Status to view the firmware version.
    Affected if The version displayed falls within these ranges: 7.0.0 through 7.0.10, 7.2.0 through 7.2.10, 7.4.0 through 7.4.7, or 7.6.0 through 7.6.3.
  2. Verify CLI access is enabled
    Confirm that the FortiWeb CLI interface is accessible. This is typically enabled by default for administrator profiles. Check via the web UI under System > Admin > Administrators or via 'show system admin' in CLI.
    Affected if CLI access is available to any administrative user accounts on the system.
  3. Identify privileged CLI users
    Review the list of administrator accounts with privileged access. In CLI, use 'get system admin' or check System > Admin > Administrators in the web UI to see which accounts have sufficient privileges to execute CLI commands.
    Affected if There are one or more administrator accounts with CLI command execution privileges (not read-only accounts).
  4. Check for unauthorized CLI command execution
    Review FortiWeb logs for suspicious or unexpected CLI commands. Use 'execute log filter category event' and then 'execute log display' to inspect recent CLI activity, looking for commands that appear unusual or malicious.
    Affected if Logs show CLI commands that were not initiated by authorized administrators, or commands containing unusual character sequences that may indicate injection attempts.

Your FortiWeb instance is affected if it runs a version within 7.0.0-7.0.10, 7.2.0-7.2.10, 7.4.0-7.4.7, or 7.6.0-7.6.3 and has CLI access available to privileged users.

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.0.11 / 7.2.11 / 7.4.8 or later
Fixed in 7.0.117.2.117.4.8
Interim mitigation

Apply Fortinet's patches: upgrade to version 7.6.4 or later, 7.4.8 or later, 7.2.11 or later, or 7.0.10 or later. Restrict CLI access to only necessary privileged personnel and monitor for unauthorized command execution.

Recommended fix High confidence

7.0.11 or later for 7.0.x branch; 7.2.11 or later for 7.2.x branch; 7.4.8 or later for 7.4.x branch; 7.6.4 or later for 7.6.x branch

  1. 1. Identify the currently running FortiWeb version by navigating to System -> Status in the FortiWeb GUI or using 'get system status' in the CLI
  2. 2. Determine which version branch you are on (7.0.x, 7.2.x, 7.4.x, or 7.6.x)
  3. 3. Download the appropriate firmware upgrade from Fortinet Customer Support portal (https://support.fortinet.com/) for your version branch
  4. 4. Backup the FortiWeb configuration via System -> Maintenance -> Backup & Restore in the GUI or 'execute backup full-config' CLI command
  5. 5. Upload the firmware file via System -> Maintenance -> Firmware in the GUI or 'execute firmware upgrade' CLI command
  6. 6. Reboot the device to apply the new firmware
  7. 7. After reboot, verify the upgrade was successful by checking the version in System -> Status or using 'get system status' and confirm the version is 7.0.11+, 7.2.11+, 7.4.8+, or 7.6.4+
Caveat Major firmware upgrades may introduce configuration changes; review Fortinet release notes for migration considerations 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-27759 — 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-27759 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