FortiwebApplication · Fortinet
CVE-2025-58034
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 · uneditedAn Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability [CWE-78] 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.10, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an authenticated attacker to execute unauthorized code on the underlying system via crafted HTTP requests or 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 confidenceOS Command Injection (CWE-78) in Fortinet FortiWeb allows authenticated attackers to execute arbitrary code on the underlying system via crafted HTTP requests or CLI commands. The vulnerability affects versions 7.0.0-7.0.11, 7.2.0-7.2.11, 7.4.0-7.4.10, 7.6.0-7.6.5, and 8.0.0-8.0.1.
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.12>= 7.2.0, < 7.2.12>= 7.4.0, < 7.4.11>= 7.6.0, < 7.6.6>= 8.0.0, < 8.0.2CVSS 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 versionLog into the FortiWeb administrative interface (web UI or CLI) and navigate to System > Status to view the firmware version, or run 'get system status' command in the CLIAffected if The displayed version falls within any of these ranges: 7.0.0-7.0.11, 7.2.0-7.2.11, 7.4.0-7.4.10, 7.6.0-7.6.5, or 8.0.0-8.0.1
-
Verify administrative access exposureCheck the network configuration to determine if the FortiWeb admin interface (HTTP/HTTPS for web UI, SSH for CLI) is accessible from untrusted networks. Review firewall policies and interface bindings under Network > InterfaceAffected if The administrative interfaces are reachable from networks that are not explicitly trusted or are exposed to the internet
-
Review user accounts and privilegesExamine the user account configuration under System > Admin > Administrators to identify accounts with privileged access that could be used to exploit this vulnerabilityAffected if There are user accounts with administrative privileges, especially those with weak or default credentials or those that are no longer in active use
-
Check for suspicious system processes or trafficIf accessible, review system logs under Log & Report > System Events and monitor for unexpected shell processes or outbound connections originating from the FortiWeb applianceAffected if There are logs or evidence of unexpected command execution, unusual outbound network traffic, or processes that were not initiated by known administrative activities
You are affected if your FortiWeb version is within 7.0.0-7.0.11, 7.2.0-7.2.11, 7.4.0-7.4.10, 7.6.0-7.6.5, or 8.0.0-8.0.1 AND the admin interface is accessible to untrusted users who could authenticate and inject OS commands.
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.127.2.127.4.11
Upgrade FortiWeb to a patched version beyond the affected releases. If immediate patching is not feasible, restrict administrative access to trusted IP addresses and audit all administrative accounts for necessity.
Upgrade to FortiWeb 7.0.12 (for 7.0.x), 7.2.12 (for 7.2.x), 7.4.11 (for 7.4.x), or 7.6.6 (for 7.6.x)
- 1. Identify the currently installed FortiWeb version by running: get system status or via the web UI under Dashboard > Status
- 2. Based on your current major version branch, upgrade to the first fixed release: For 7.0.x upgrade to 7.0.12, for 7.2.x upgrade to 7.2.12, for 7.4.x upgrade to 7.4.11, or for 7.6.x upgrade to 7.6.6
- 3. Download the firmware from the Fortinet Customer Support portal: https://customerportal.fortinet.com/
- 4. Upload the firmware via the FortiWeb web UI under System > Maintenance > Firmware or via CLI using execute restore config or execute upgrade
- 5. After upgrade, verify the version using get system status and confirm the vulnerability is resolved
- 6. Review the FortiWeb hardened configuration to ensure least privilege for administrative accounts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiweb
Exploited in the wild — priority engagement
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58034 — 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-58034 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