Exploited CVEs / Fortinet / CVE-2025-58034

CVE-2025-58034

Fortinet FortiWeb OS Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2025-11-25 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Fortinet PSIRT Advisories, linked below.

Risk summary

HighCISA KEV

7.2

CVSS base

56%

EPSS exploit probability

High

Severity

2025-11-18

Added to KEV

2025-11-25 (past due)

CISA due date

Actively exploited Fortinet FortiWeb vulnerability, High severity, CVSS 7.2. Added to the CISA KEV catalog 2025-11-18.

Senserva AI read on CVE-2025-58034 CISA required action Official fix for CVE-2025-58034 Admin questions

Senserva AI Opinion for CVE-2025-58034

Unlike most FortiWeb entries in the KEV catalog, this OS command injection requires authentication, which is why its CVSS sits at 7.2 rather than critical. It still earns urgency: EPSS estimates a 54% exploit probability, CISA confirmed attacks in November 2025, and it pairs naturally with any credential theft or authentication bypass on the same appliance.

Do this: Update FortiWeb to the fixed release and review admin session logs for unfamiliar CLI or HTTP activity.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2025-58034

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2025-58034, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2025-58034.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-58034: Fortinet FortiWeb OS Command Injection Vulnerability
- Affected: Fortinet FortiWeb
- Severity: High, CVSS 7.2; EPSS 30-day exploitation probability 56%
- Added to CISA KEV: 2025-11-18; federal remediation due 2025-11-25
- Ransomware-linked: no
- CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Fortinet PSIRT Advisories.

Do this now: Federal remediation deadline 2025-11-25; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 15, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2025-58034

Published: 2025-11-18
Last revised: 2025-11-18
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2025-11-18 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 7.2; EPSS first scored at 55.6%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2025-11-25 (past due).

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Official fix for CVE-2025-58034

The authoritative fix and affected-version list are published by the vendor. Find the FortiWeb advisory on Fortinet PSIRT Advisories.

Fortinet PSIRT Advisories CISA KEV entry

Common questions about CVE-2025-58034

Is CVE-2025-58034 actively exploited?

Yes. CVE-2025-58034 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2025-11-18, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 56%.

What is the CISA deadline and required action for CVE-2025-58034?

CISA set the federal (BOD 22-01) remediation due date at 2025-11-25, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2025-58034?

The authoritative fix is in the vendor advisory: see Fortinet PSIRT Advisories for the patched FortiWeb versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2025-58034?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2025-58034's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Fortinet CVEs: CVE-2025-68686 CVE-2026-39808 CVE-2026-25089 CVE-2026-21643 CVE-2026-35616 CVE-2026-24858 CVE-2025-59718 CVE-2025-64446
All Fortinet exploited CVEs on one page: Fortinet vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.