Skip to content
Fencer Vulns
medium 4.8

CVE-2024-50562 json

An Insufficient Session Expiration vulnerability [CWE-613] in FortiOS SSL-VPN version 7.6.0, version 7.4.6 and below, version 7.2.10 and be…

published 2025-06-10 16 mo ago modified 2026-10-15 25 d ago also EUVD-2025-17805

cvss
4.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
1
Exploit-DB

Summary

An Insufficient Session Expiration vulnerability [CWE-613] in FortiOS SSL-VPN version 7.6.0, version 7.4.6 and below, version 7.2.10 and below, 7.0 all versions, 6.4 all versions may allow an attacker in possession of a cookie used to log in the SSL-VPN portal to log in again, although the session has expired or was logged out.

Patch / fix

  • fortinet fortios 7.2.11, 7.4.8

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-25-135-01 updated cvss 4.8

Siemens RUGGEDCOM APE1808 Devices

  • Siemens RUGGEDCOM APE1808
    affected: fixed in V7.4.9

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Timeline

  1. Published
  2. First public exploit (EDB-52336)

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
16 mo ago

Exploit prediction

1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-52336 FortiOS SSL-VPN 7.4.4 - Insufficient Session Expiration & Cookie Reuse remote, 2025-06-20

CVSS scores

assigned by version score vector
CNA 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P/RL:X/RC:R
CNA 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • Fortinet FortiOS
  • Fortinet FortiPAM
  • Fortinet FortiProxy
  • Siemens RUGGEDCOM APE1808

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.