CVE-2025-64471VulnerabilityPublished 9 Dec 2025Updated 14 Jan 2026

CVE-2025-64471: Fortinet FortiWeb · Escalation of privilege

Affects Fortinet FortiWebSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiWeb	Affected =8.0.0 =7.6.0 =7.4.0 =7.2.0 =7.0.0	Fixed in–

AI-suggested

1. Immediately implement network segmentation to restrict access to FortiWeb management interfaces, limiting exposure to trusted administrative networks only. 2. Deploy strict firewall rules and access control lists (ACLs) to block unauthorized HTTP/HTTPS traffic targeting FortiWeb devices. 3. Enable and monitor detailed logging on FortiWeb appliances to detect anomalous authentication attempts or unusual request patterns indicative of exploitation attempts. 4. Use intrusion detection/prevention systems (IDS/IPS) with updated signatures to identify and block crafted requests exploiting this vulnerability. 5. Establish a vulnerability management process to track Fortinet advisories and apply patches or firmware updates as soon as they become available. 6. Conduct regular security audits and penetration tests focusing on FortiWeb configurations and access controls. 7. Educate network and security teams about this vulnerability to ensure rapid response and incident handling. 8. Consider deploying multi-factor authentication (MFA) for FortiWeb administrative access to add an additional security layer, mitigating risks from compromised credentials or hashes. 9. If possible, temporarily disable remote management interfaces or restrict them to VPN access until patches are applied. 10. Collaborate with Fortinet support for guidance and early access to patches or workarounds.

Description

A use of password hash instead of password for authentication vulnerability [CWE-836] 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 unauthenticated attacker to use the hash in place of the password to authenticate via crafted HTTP/HTTPS requests

Impact

For European organizations, the impact of CVE-2025-64471 can be substantial, particularly for those using FortiWeb appliances to secure critical web applications and infrastructure. Successful exploitation allows attackers to escalate privileges within the FortiWeb device, potentially enabling unauthorized configuration changes, bypassing security policies, or gaining deeper network access. This compromises the integrity of the security controls, increasing the risk of further attacks such as data manipulation or lateral movement within the network. Although confidentiality and availability are not directly impacted, the loss of integrity in security appliances can indirectly lead to data breaches or service disruptions. Organizations in sectors like finance, government, healthcare, and telecommunications, which heavily rely on Fortinet products for web application protection, face elevated risks. The vulnerability's network-based attack vector means that attackers can attempt exploitation remotely, increasing the threat surface. However, the requirement for crafted requests and some privilege conditions may limit widespread exploitation. Still, the absence of patches at disclosure heightens the urgency for European entities to implement interim protective measures.

References

fortiguard.fortinet.com/psirt/FG-IR-25-984 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:51 UTC

Technical details

References

Community reviews

Related threats