CVE-2025-64447
Fortinet Fortiweb 7.0.0 – 7.0.11
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-64447 is a high-severity Reliance on Cookies without Validation and Integrity Checking (CWE-565) vulnerability in Fortinet Fortiweb. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Web Session Cookie (T1550.004); ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-64447 is a vulnerability stemming from reliance on cookies without validation and integrity checking, classified under CWE-565, in Fortinet FortiWeb web application firewall. The issue affects FortiWeb versions 8.0.0 through 8.0.1, 7.6.0 through 7.6.5, 7.4.0 through 7.4.10, 7.2.0 through 7.2.11, and 7.0.0 through 7.0.11. It carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting high severity due to potential for significant impacts across confidentiality, integrity, and availability.
An unauthenticated attacker can exploit this vulnerability by crafting HTTP or HTTPS requests with forged cookies, provided they have prior knowledge of the target's FortiWeb serial number. Successful exploitation enables execution of arbitrary operations on the system, though it requires high attack complexity.
Mitigation details are outlined in the Fortinet PSIRT advisory available at https://fortiguard.fortinet.com/psirt/FG-IR-25-945. Security practitioners should consult this reference for patching instructions and workarounds applicable to affected versions.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202281
Vulnerability Data
A reliance on cookies without validation and integrity checking 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 execute arbitrary…
more
operations on the system via crafted HTTP or HTTPS request via forged cookies, requiring prior knowledge of the FortiWeb serial number.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Access Enforcement requires authorizations to be enforced by the system rather than by trusting client-supplied cookie values.
Session Authenticity directly requires protecting the integrity and authenticity of session tokens such as cookies, eliminating blind reliance on them.
Transmission Confidentiality and Integrity mandates cryptographic or equivalent protection for data in transit, which covers cookie values exchanged over HTTP.
Software, Firmware, and Information Integrity can detect unauthorized modification of cookie-based data after the fact via integrity verification.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Cookies commonly carry identity assertions; requiring their protection, conveyance, and verification directly eliminates the weakness.
Strong authentication mechanisms reduce reliance on unvalidated cookies for identity and access decisions.
Cryptographic integrity for data-in-transit directly mitigates tampering of cookies sent over the network.
Enforcing access policy and least privilege limits damage from cookie misuse but does not address cookie validation itself.
Integrity protections for data-at-rest can apply to cookie stores but do not cover validation during use.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect cookie-validation flaws but does not itself implement the required controls.
Application security requirements can mandate cookie validation, integrity protection, and server-side session handling.
Secure coding practices directly eliminate reliance on unvalidated cookies by requiring proper integrity checks and server-side verification.
Secure authentication mechanisms can enforce server-side validation and integrity checks that prevent reliance on untrusted cookies.