CVE-2025-25257: Fortinet FortiWeb SQL Injection Vulnerability
Affects Fortinet FortiWebSource CISA KEV
Exploited in the wild · KEV due 8 Aug 2025 · public exploit available (Exploit-DB) · 99% EPSS : apply the vendor's fix or mitigations to Fortinet FortiWeb now.
Data as of 10/24/2026, 22:16:00 UTC
- Exploitation
Actively exploited – in CISA KEV since 07/18/2025
- KEV deadline
- 08/08/2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
- EPSS
- 99.9% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Public exploits
- 1 Exploit-DB entry, a Nuclei detection templatePublic attack or detection tooling exists; see Public exploits below.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:CWhat to do
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.
Check the firmware or software version for Fortinet FortiWeb in the device's admin interface against the vendor advisory.
Public exploits and detection
Nuclei detection templates
Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.
Description
Fortinet FortiWeb contains a SQL injection vulnerability that may allow an unauthenticated attacker to execute unauthorized SQL code or commands via crafted HTTP or HTTPs requests.
Weaknesses
- CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.