dbcve.org
FortiadcApplication · Fortinet

CVE-2025-31104

HIGH · 7.2 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 7.1.5 / 7.2.8 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 FortiADC 7.6.0 through 7.6.1, 7.4.0 through 7.4.6, 7.2.0 through 7.2.7, 7.1.0 through 7.1.4, 7.0 all versions, 6.2 all versions, 6.1 all versions may allow an authenticated attacker to execute unauthorized code via crafted HTTP 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

FortiADC web interface contains an OS command injection vulnerability where crafted HTTP requests with malicious payload can be interpreted by the underlying system shell. An authenticated attacker can inject OS commands through HTTP parameters, allowing arbitrary code execution on the appliance.

MitigationApply Fortinet's patched FortiADC version (contact Fortinet for specific fixed releases). Restrict administrative access to trusted IPs and monitor for unusual HTTP request patterns.

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.1.0, < 7.1.5>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.7>= 7.6.0, < 7.6.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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Identify the FortiADC version
    Log into the FortiADC CLI or web UI and locate the system version information. In the web UI, this is typically found under System > Firmware or in the dashboard. In CLI, use the command 'get system status' to retrieve the firmware version.
    Affected if The installed version falls within these vulnerable ranges: 6.1.0 through 7.1.4, 7.2.0 through 7.2.7, 7.4.0 through 7.4.6, or 7.6.0 through 7.6.1.
  2. Confirm the web interface is enabled
    In the FortiADC web UI, navigate to System > Administration > Admin Settings or check the interface configuration to verify if the HTTP/HTTPS administrative web interface is enabled and bound to accessible network interfaces.
    Affected if The web interface is enabled and reachable from network segments where untrusted users could potentially authenticate.
  3. Verify administrative access controls
    Review the administrative access settings to determine if source IP restrictions are configured. Check under System > Administration > Admin Settings or the specific admin user profiles to see if trusted IP restrictions are applied.
    Affected if Administrative access is open to untrusted IP addresses or there are no IP-based restrictions on the web interface.
  4. Check for existing compromised indicators
    Review FortiADC logs under Log & Report > System Events or Log & Report > Traffic for unusual HTTP requests, especially those containing suspicious characters like semicolons, pipes, or command substitution operators in parameter values.
    Affected if Logs show anomalous HTTP requests with command injection patterns or unexpected command executions.

You are affected if your FortiADC firmware version is within the vulnerable ranges AND the web interface is accessible to authenticated but untrusted 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.1.5 / 7.2.8 / 7.4.7 or later
Fixed in 7.1.57.2.87.4.7
Interim mitigation

Apply Fortinet's patched FortiADC version (contact Fortinet for specific fixed releases). Restrict administrative access to trusted IPs and monitor for unusual HTTP request patterns.

Recommended fix High confidence

Upgrade to 7.1.5+ (for 6.x/7.0/7.1 branches), 7.2.8+ (for 7.2 branch), 7.4.7+ (for 7.4 branch), or 7.6.2+ (for 7.6 branch)

  1. 1. Identify the current FortiADC version by navigating to FortiADC UI > Dashboard > System Information or running 'get system status' in CLI.
  2. 2. Based on your current version, determine the minimum upgrade target: For 6.1.x, 6.2.x, 7.0.x → upgrade to 7.1.5 or later. For 7.1.x → upgrade to 7.1.5 or later. For 7.2.x → upgrade to 7.2.8 or later. For 7.4.x → upgrade to 7.4.7 or later. For 7.6.0-7.6.1 → upgrade to 7.6.2 or later.
  3. 3. Before upgrading, backup the current configuration via FortiADC UI > Maintenance > Backup & Restore or CLI 'execute backup full-config' to a secure location.
  4. 4. Review Fortinet release notes for the target version to verify compatibility with your deployment and any known migration considerations.
  5. 5. Perform the upgrade: In FortiADC UI, go to System > Firmware > Upload Firmware and select the appropriate firmware file, then click Upgrade. Alternatively, in CLI use 'execute firmware upgrade <image_name>' after uploading the firmware to the device.
  6. 6. After reboot, verify the upgrade was successful by checking the firmware version in System Information and confirming all services are operational.
  7. 7. Validate that the vulnerability is resolved by confirming the version is at or above the fixed release for your branch.
Caveat Major version jumps (e.g., 6.x to 7.x) may introduce configuration or behavioral changes—review release notes for breaking changes before upgrading

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-2025-31104 — 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-31104 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