Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2024-21762

FortiProxy

Fortinet / FortiProxy · affected before 2.0.14

Watch CVE-2024-21762 Browse KEV feed
Severity
CVSS 9.6 · Critical
Confidence
Confirmed
Exploit status
Exploited in the wild
EPSS
83.4%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2024-21762 is an unauthenticated vulnerability affecting Fortinet FortiProxy, FortiOS. A out-of-bounds write in Fortinet FortiOS versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.13, 6.4.0...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV. Also confirmed by third-party sources.

Who is affected?

Fortinet / FortiProxy affected before 2.0.14.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

FortiProxy

A out-of-bounds write in Fortinet FortiOS versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.6, 7.0.0 through 7.0.13, 6.4.0 through 6.4.14, 6.2.0 through 6.2.15, 6.0.0 through 6.0.17, FortiProxy versions 7.4.0 through 7.4.2, 7.2.0 through 7.2.8, 7.0.0 through 7.0.14, 2.0.0 through 2.0.13, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7 allows attacker to execute unauthorized code or commands via specifically crafted requests

fortinet Affected
fortiproxy
Before 2.0.14 Before 7.0.15 Before 7.2.9 Before 7.4.3
fortinet Affected
fortios
Before 6.2.16 Before 6.4.15 Before 7.0.14 Before 7.2.7 Before 7.4.3
Fortinet Affected
FortiProxy
Through 7.4.2 Through 7.2.8 Through 7.0.14 Through 2.0.13 Through 1.2.13 Through 1.1.6 Through 1.0.7
Fortinet Affected
FortiOS
Through 7.4.2 Through 7.2.6 Through 7.0.13 Through 6.4.14 Through 6.2.15 Through 6.0.17
Published
09 Feb 2024
Exploitation Reported
09 Feb 2024
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nessus_scanner edge cisa ios malware

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 09 Feb 2024

A trusted third party reported exploitation.

Used in malware

CISA

Recorded 02 Jun 2026

Malware families have been linked to exploitation of this CVE.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2024-02-09 00:00 UTC
CVE 2026-08-04 04:41 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Nessus https://www.tenable.com/plugins/nessus/114795 02 Jun 2025

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.6 Critical

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

83.4%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Out-of-bounds Write CWE-787

Recent mention · The Hacker News

3BB Attacker Used MeshCentral Backdoor for Root Access, Targeted Subscriber Credentials

An attacker was operating inside the network of 3BB, one of Thailand's largest broadband providers, and maintained remote control of internal machines using a legitimate management tool called MeshCentral, threat intelligence firm Hunt.io said. The company uncovered the...

Read full advisory

All Mentions

Recent mention · The Hacker News

3BB Attacker Used MeshCentral Backdoor for Root Access, Targeted Subscriber Credentials

The Hacker News · 14 Sep 2026

An attacker was operating inside the network of 3BB, one of Thailand's largest broadband providers, and maintained remote control of internal machines using a legitimate management tool called MeshCentral, threat intelligence firm Hunt.io said. The company uncovered the intrusion by examining a server the attacker had left open on the internet, which held the attacker's own tools and a list of

Recent mention · Tenable Blog

CVE-2025-32756: Zero-Day Vulnerability in Multiple Fortinet Products Exploited in the Wild

Tenable Blog · 14 May 2025

Fortinet has observed threat actors exploiting CVE-2025-32756, a critical zero-day arbitrary code execution vulnerability which affects multiple Fortinet products including FortiVoice, FortiMail, FortiNDR, FortiRecorder and FortiCamera.BackgroundOn May 13th, Fortinet published a security advisory (FG-IR-25-254) for CVE-2025-32756, a critical arbitrary code execution vulnerability affecting multiple Fortinet products.CVEDescriptionCVSSv3CVE-2025-32756An arbitrary code execution vulnerability in FortiVoice, FortiMail, FortiNDR, FortiRecorder and FortiCamera9.6AnalysisCVE-2025-32756 is an...

Recent mention · Tenable Blog

Cybersecurity Snapshot: U.K. NCSC’s Best Cyber Advice on AI Security, the Quantum Threat, API Risks, Mobile Malware and More

Tenable Blog · 09 May 2025

In this special edition of the Cybersecurity Snapshot, we bring you some of the most valuable guidance offered by the U.K. National Cyber Security Centre (NCSC) in the past 18 months. Check out best practices, recommendations and insights on protecting your AI systems, APIs and mobile devices, as well as on how to prep for post-quantum cryptography, and more.In case you missed it, here are six NCSC recommendations to help your organization fine-tune its cybersecurity strategy and operations.1 - How to migrate to quantum-resistant cryptographyIs your organization planning to adopt...

Recent mention · Tenable Blog

Reducing Remediation Time Remains a Challenge: How Tenable Vulnerability Watch Can Help

Tenable Blog · 25 Apr 2025

Timely vulnerability remediation is an ongoing challenge for organizations as they struggle to prioritize the exposures that represent the greatest risk to their operations. Existing scoring systems are invaluable but can lack context. Here’s how Tenable’s Vulnerability Watch classification system can help.BackgroundOver the past six years working in Tenable’s research organization, I’ve watched known vulnerabilities and zero-day flaws plague organizations in the immediate aftermath of disclosure or even years afterwards. Following each blog post or threat report we’ve published, I kept...

Timeline

From disclosure to observed exploitation

  1. 04:41 UTC

    KEV confirmed by CVE

    Exploitation attested by an external source

  2. 14:08 UTC

    First public exploitation report

    Exploit observed in malware

  3. 09:26 UTC

    Nessus plugin available

    Scanner coverage available

  4. 08:14 UTC

    CVE published

    Vulnerability disclosed publicly

  5. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  6. 10:15 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2024-21762

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2024-21762",
  "confidence": "Confirmed",
  "cvss_score": 9.6,
  "cvss_estimated": false,
  "epss_score": 0.83428,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}