CVE-2025-52970
Description revised (poc_count, poc_public, poc_url). The record changed; nothing in the observed threat did.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: fortiweb 7.0.11; fortiweb 7.2.11; fortiweb 7.4.8; fortiweb 7.6.4 upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A improper handling of parameters in Fortinet FortiWeb versions 7.6.3 and below, versions 7.4.7 and below, versions 7.2.10 and below, and 7.0.10 and below may allow an unauthenticated remote attacker with non-public information pertaining to the device and targeted user to gain admin privileges on the device via a specially crafted request.
- weakness
- CWE-233 Improper access control
- affected
- Fortinet FortiWeb
- published ranges
- fortinet fortiweb >= 7.0.0 < 7.0.11; fortinet fortiweb >= 7.2.0 < 7.2.11; fortinet fortiweb >= 7.4.0 < 7.4.8; fortinet fortiweb >= 7.6.0 < 7.6.4
- first unaffected version, by branch
- fortiweb 7.0.11; fortiweb 7.2.11; fortiweb 7.4.8; fortiweb 7.6.4
- severity
- 7.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:C
- assigned by
- fortinet
- published
- 2025-08-12
check us fortiguard.fortinet.com
Exploit code held, dated
- exploit code
- 2 public proof-of-concept repositories, first seen 2025-08-23 (PoC-in-GitHub).
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 13 Aug 2025 | 0.00093 | |
| 16 Aug 2025 | 0.00245 | |
| 18 Aug 2025 | 0.00322 | |
| 13 Sep 2025 | 0.00351 | |
| 19 Dec 2025 | 0.18952 | crossed 0.10 |
| 15 Jun 2026 | 0.1067 | scoring model v2026.06.15 |
| 13 Jul 2026 | 0.09825 | crossed 0.10 |
| 9 Sep 2026 | 0.09746 | |
| 27 Sep 2026 | 0.10084 | crossed 0.10 |
28 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.10 on 2026-09-27 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 50% (0.50). Crossing a line changes this brief.
- fix
- Held: fortiweb 7.0.11; fortiweb 7.2.11; fortiweb 7.4.8; fortiweb 7.6.4. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-52970', '2026-10-30T23:59:59.999999Z', now());