dbcve.org
FortiadcApplication · Fortinet

CVE-2025-49813

HIGH · 7.2 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 7.1.2 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 Fortinet FortiADC version 7.2.0 and before 7.1.1 allows a remote and authenticated attacker with low privilege to execute unauthorized code via specifically crafted HTTP parameters.

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 FortiADC's web interface allows an authenticated attacker with low-privilege access to execute arbitrary OS commands by injecting malicious commands into HTTP parameters. The vulnerability stems from improper neutralization of special elements in user-supplied HTTP parameter values.

MitigationUpgrade FortiADC to version 7.1.2 or later (or 7.2.1+ if available). If immediate patching is not possible, restrict administrative interface access to trusted IPs only and monitor for suspicious HTTP requests containing shell metacharacters.

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.2.0, <= 6.2.6>= 7.1.0, < 7.1.2= 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
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 FortiADC version
    Log into the FortiADC CLI and run the command 'get system status' or access the web UI to view the dashboard which displays the firmware version
    Affected if The displayed version falls within 6.2.0 to 6.2.6, 7.1.0 to 7.1.1, or 7.2.0
  2. Confirm web interface access is enabled
    In the FortiADC CLI, run 'show system interface' to list network interfaces and their HTTP/HTTPS settings, or check via web UI under Network > Interfaces
    Affected if The management or any interface has HTTP or HTTPS access enabled, making the web interface reachable
  3. Verify low-privilege user accounts exist
    In the web UI, go to System > Administrator > Administrators to list all admin accounts and their access profiles, or run 'show system admin' in CLI
    Affected if There are administrator accounts with limited or low-privilege access profiles (non-super_admin) that can log into the web interface
  4. Check for command injection indicators in logs
    In the web UI, go to Log & Report > Event Log and filter for events containing shell metacharacters like ';', '|', '`', '$', or '&&' in HTTP parameter values, or grep the system logs via CLI
    Affected if Recent logs show suspicious HTTP requests with shell metacharacters in parameter values, indicating potential exploitation attempts

You are affected if your FortiADC version is 6.2.0-6.2.6, 7.1.0-7.1.1, or 7.2.0 AND the web interface is accessible to low-privilege authenticated 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.2 or later
Fixed in 7.1.2
Interim mitigation

Upgrade FortiADC to version 7.1.2 or later (or 7.2.1+ if available). If immediate patching is not possible, restrict administrative interface access to trusted IPs only and monitor for suspicious HTTP requests containing shell metacharacters.

Recommended fix High confidence

7.1.2 or 7.2.1 (depending on which major branch you are on)

  1. 1. Identify the currently installed FortiADC version using 'get system status' or through the web UI under Dashboard > Status
  2. 2. Determine the appropriate upgrade path based on current version: if on 6.2.x line, upgrade to 6.2.7 or later; if on 7.1.x line, upgrade to 7.1.2 or later; if on 7.2.x line, upgrade to 7.2.1 or later
  3. 3. Backup the current FortiADC configuration via 'execute backup config' or through the web UI under System > Maintenance > Backup & Restore
  4. 4. Download the firmware upgrade from Fortinet customer support portal or FortiGuard
  5. 5. Upload the new firmware file via 'execute upgrade' command or through the web UI under System > Firmware
  6. 6. Reboot the device to apply the new firmware using 'execute reboot'
  7. 7. After reboot, verify the new version is installed using 'get system status'
  8. 8. Confirm the vulnerability is resolved by checking that the installed version is no longer in the affected versions list
Caveat Minor firmware upgrades typically maintain configuration compatibility; backup before upgrading as standard practice

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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