Threats / Fortinet / CVE-2025-25257
CVE-2025-25257
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Fortinet FortiWeb vulnerability
Fortinet FortiWeb contains a SQL injection vulnerability allowing unauthenticated attackers to execute arbitrary SQL commands via crafted HTTP requests.
Verdict
Today item — known-exploited.
An unauthenticated remote attacker can exploit SQL injection in FortiWeb to execute unauthorized database commands, potentially leading to data exfiltration, modification, or denial of service. Active exploitation has been observed in the wild.
CISA KEV Yes · 2025-07-185EPSS 0.9671 (verify live)6Exploit Weaponized · public PoC7CVSS 9.63CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
282 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-18).
Probability (EPSS)
EPSS 0.9671 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:C) · Affected: Fortinet, FortiWeb. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious HTTP requests containing SQL injection payloads targeting FortiWeb's input validation.
Business
Attackers gain unauthorized database access without authentication, bypassing security controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary SQL commands to extract sensitive data from the application database.
Business
Confidential information including credentials, configuration data, and customer records are compromised.
3
Lateral reach — past segmentation narrative 3
Attacker
I modify or delete database records to alter application behavior or destroy audit trails.
Business
Data integrity is compromised, system functionality is disrupted, and forensic investigation becomes difficult.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05