FortiwebApplication · Fortinet
CVE-2025-66178
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 · uneditedA improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.5, FortiWeb 7.4.0 through 7.4.11, FortiWeb 7.2.0 through 7.2.12, FortiWeb 7.0.0 through 7.0.12 may allow an authenticated attacked to execute arbitrary commands via a specialy crafted HTTP request.
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 confidenceOS command injection vulnerability in FortiWeb's web management interface. An authenticated attacker can execute arbitrary operating system commands by sending specially crafted HTTP requests containing malicious command payloads that are improperly sanitized before being passed to system shell 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
>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.13>= 7.4.0, < 7.4.12>= 7.6.0, < 7.6.7>= 8.0.0, < 8.0.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiWeb installed versionAccess the FortiWeb CLI and run the command 'get system status' or 'fwb -v' to retrieve the installed firmware version. Alternatively, log into the web management interface and navigate to System > Status to view the firmware version.Affected if The displayed version falls within any of these ranges: 7.0.0-7.0.12, 7.2.0-7.2.12, 7.4.0-7.4.11, 7.6.0-7.6.6, or 8.0.0-8.0.2.
-
Verify web management interface is enabledIn the FortiWeb CLI, run 'show system interface' to list network interfaces and confirm the web management HTTP/HTTPS service is active. Check if port 80 or 443 (or configured alternative ports) are listening.Affected if The web management interface is exposed and reachable from network segments where untrusted users could potentially obtain credentials.
-
Confirm administrative access methodsReview administrative user accounts and access profiles using 'show system admin' in the CLI. Check if remote authentication (RADIUS, LDAP) is configured and if administrative access is permitted from any IP address.Affected if Administrative accounts exist that can access the web management interface, particularly if access is allowed from non-restricted IP addresses.
-
Audit recent web management access logsExamine FortiWeb logs for the web management interface. Look for POST requests to administrative endpoints, especially those containing unusual characters such as ';', '|', '&', '`', or '$' in parameter values.Affected if Suspicious HTTP requests with command injection patterns are found in the logs, indicating potential exploitation attempts.
A FortiWeb instance is affected if it runs a version within the vulnerable ranges AND has an accessible web management interface with valid administrative credentials in use.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.0.137.2.137.4.12
Apply vendor-supplied patches for affected FortiWeb versions (7.0.12+, 7.2.12+, 7.4.11+, 7.6.5+, 8.0.1+). Prior to patching, restrict administrative access to trusted IP addresses and monitor for suspicious HTTP requests containing command separators.
FortiWeb 7.0.13 (or latest 7.0.x), 7.2.13 (or latest 7.2.x), 7.4.12 (or latest 7.4.x), or 7.6.7 (or latest 7.6.x) depending on your current major branch
- 1. Identify the currently installed FortiWeb version via Web UI (System > Status) or CLI: `get system status`
- 2. Based on your current major version, plan upgrade to the minimum fixed version: For 7.0.x upgrade to 7.0.13+, for 7.2.x upgrade to 7.2.13+, for 7.4.x upgrade to 7.4.12+, for 7.6.x upgrade to 7.6.7+
- 3. Backup the FortiWeb configuration via Web UI (System > Maintenance > Backup & Restore) or CLI: `execute backup full-config`
- 4. Download the appropriate firmware upgrade from Fortinet support portal (support.fortinet.com)
- 5. Upload and install the new firmware via Web UI (System > Maintenance > Firmware) or CLI: `execute restore image <filename>`
- 6. After reboot, verify the new version is running and confirm all services are operational
- 7. Verify the fix by checking FortiWeb version: `get system status`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66178 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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