IRONSMITHINTEL
HIGHCVSS7.2
|
Actively Exploited
|CISA KEV|CVE-2025-58034|Auth: high — administrative privileges|Reboot: required|Manual only

Fortinet FortiWeb OS Command Injection Vulnerability (CVE-2025-58034)

Fortinet FortiWeb contains an OS command Injection vulnerability that may allow an authenticated attacker to execute unauthorized code on the underlying system via crafted HTTP requests or CLI commands.

Published Nov 18, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, with administrative privileges, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-11-25 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a OS Command Injection (CWE-78) vulnerability in Fortinet FortiWeb. An 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. Exploitation requires remote network access, low attack complexity, an administrative account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●Network Security Team
●Firewall Administrators
●IT Security
●Running fortiweb: 7.0.0 ≤ v < 7.0.12, 7.2.0 ≤ v < 7.2.12, 7.4.0 ≤ v < 7.4.11, 7.6.0 ≤ v < 7.6.6, 8.0.0 ≤ v < 8.0.2
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-11-18 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-11-25.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2025-58034's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2025-58034↗ MSRC Advisory↗ NVD↗ Vendor Advisory