CVE-2025-24472
An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS 7.0.0 through 7.0.16 and FortiProxy 7.2.0 through 7.2.12, 7.0.0 through 7.0.19 may allow a remote unauthenticated attacker with prior knowledge of upstream and downstream devices serial numbers to gain super-admin privileges on the downstream device, if the Security Fabric is enabled, via crafted CSF proxy requests.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-24472 being exploited?
Yes. CVE-2025-24472 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-24472?
CVE-2025-24472 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-24472?
Yes. A fix has been recorded for CVE-2025-24472. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-24472 affect?
CVE-2025-24472 affects fortinet:fortiproxy, fortinet:fortios. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 7.0.0 and <= 7.0.16
- affected>= 7.2.0 and <= 7.2.12
- affected>= 7.0.0 and <= 7.0.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 12 Feb 2025 (SSVC 2.0.3).
timeline
- 11 Feb 2025Published
- 12 Feb 2025CISA SSVC assessment: exploitation active · same day later
- 18 Mar 2025Added to CISA KEV (exploited in the wild) · 34 days later
- 8 Apr 2025CISA remediation due date (US federal agencies) · 21 days later
- 23 Jul 2026First proof-of-concept repository on GitHub (unvetted) · 471 days (about 1 year) later
- 5 Aug 2026CVE record last updated · 13 days later
- 2 Nov 2026Analysed by vulneraibility.com · 90 days (about 3 months) later
- Linkfortiguard.fortinet.com /psirt/FG-IR-24-535
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24472
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.