CVE-2024-24809

HIGHNVD 8.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 90% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 8.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
CISA-KEV: Not listedEPSS: 54%CVSS: 8.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Traccar is an open source GPS tracking system. Versions prior to 6.0 are vulnerable to path traversal and unrestricted upload of file with dangerous type. Since the system allows registration by default, attackers can acquire ordinary user permissions by registering an account and exploit this vulnerability to upload files with the prefix device. under any folder. Attackers can use this vulnerability for phishing, cross-site scripting attacks, and potentially execute arbitrary commands on the server. Version 6.0 contains a patch for the issue.

CVSS v3
8.5
EG Score
9.0(high)
EPSS
98.9%
KEV
Not listed

Published

April 10, 2024

Last Modified

April 15, 2026

References (4)

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 07:52 UTCOSV refresh
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-09 19:09 UTCEPSS rescore
  5. 2026-07-05 02:29 UTCEPSS rescore
  6. 2026-07-01 15:05 UTCEPSS rescore
  7. 2026-06-30 23:21 UTCEPSS rescore
  8. 2026-06-30 23:21 UTCEPSS rescore
  9. 2026-06-28 04:55 UTCEPSS rescore
  10. 2026-06-28 04:55 UTCEPSS rescore
  11. 2026-06-27 03:07 UTCEPSS rescore
  12. 2026-06-27 03:07 UTCEPSS rescore
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-25 13:48 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-24 14:04 UTCEPSS rescore
  17. 2026-06-23 21:32 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-22 14:26 UTCOSV refresh
  20. 2026-06-22 14:24 UTCEPSS rescore
  21. 2026-06-22 14:24 UTCEPSS rescore
  22. 2026-06-21 01:58 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-19 19:24 UTCEPSS rescore
  25. 2026-06-19 19:24 UTCEPSS rescore
Show 47 more
  1. 2026-06-17 17:52 UTCEPSS rescore
  2. 2026-06-17 17:52 UTCEPSS rescore
  3. 2026-06-16 17:51 UTCEPSS rescore
  4. 2026-06-16 17:51 UTCEPSS rescore
  5. 2026-06-15 17:47 UTCEPSS rescore
  6. 2026-06-10 22:17 UTCEPSS rescore
  7. 2026-06-10 13:21 UTCEPSS rescore
  8. 2026-06-10 13:21 UTCEPSS rescore
  9. 2026-06-07 15:24 UTCEPSS rescore
  10. 2026-06-07 15:24 UTCEPSS rescore
  11. 2026-06-06 13:46 UTCEPSS rescore
  12. 2026-06-06 13:46 UTCEPSS rescore
  13. 2026-06-05 22:46 UTCEPSS rescore
  14. 2026-06-05 22:46 UTCEPSS rescore
  15. 2026-06-04 23:39 UTCOSV refresh
  16. 2026-06-01 13:51 UTCEPSS rescore
  17. 2026-06-01 13:51 UTCEPSS rescore
  18. 2026-06-01 13:51 UTCEPSS rescore
  19. 2026-05-31 00:15 UTCEPSS rescore
  20. 2026-05-31 00:15 UTCEPSS rescore
  21. 2026-05-28 13:44 UTCEPSS rescore
  22. 2026-05-28 13:44 UTCEPSS rescore
  23. 2026-05-28 13:44 UTCEPSS rescore
  24. 2026-05-27 13:40 UTCEPSS rescore
  25. 2026-05-27 13:40 UTCEPSS rescore
  26. 2026-05-22 21:16 UTCEPSS rescore
  27. 2026-05-22 21:16 UTCEPSS rescore
  28. 2026-05-22 21:16 UTCEPSS rescore
  29. 2026-05-22 21:16 UTCEPSS rescore
  30. 2026-05-22 03:19 UTCEG score recompute
  31. 2026-05-21 21:06 UTCOSV refresh
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 22:37 UTCEPSS rescore
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 11:21 UTCEPSS rescore
  38. 2026-05-20 11:21 UTCEPSS rescore
  39. 2026-05-20 11:21 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-20 11:21 UTCEPSS rescore
  42. 2026-05-20 11:21 UTCEPSS rescore
  43. 2026-05-18 21:30 UTCEPSS rescore
  44. 2026-05-18 21:30 UTCEPSS rescore
  45. 2026-05-18 21:30 UTCEPSS rescore
  46. 2026-05-18 21:30 UTCEPSS rescore
  47. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (2 Metasploit modules) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/http/paloalto_expedition_rce✓ verified
    First seen Oct 9, 2024

    Palo Alto Expedition Remote Code Execution (CVE-2024-5910 and CVE-2024-9464)

    Open source ↗
  • GitHub PoCgh-ost00/CVE-2024-24809-Proof-of-concept
    First seen Sep 3, 2024

    Critical Flaws in Traccar GPS System Expose Users to Remote Attacks

    Open source ↗
  • Metasploitexploit/linux/http/traccar_rce_upload✓ verified
    First seen Aug 23, 2024

    Traccar v5 Remote Code Execution (CVE-2024-31214 and CVE-2024-24809)

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-24809.yaml
    First seen Jan 1, 2024

    Traccar - Unrestricted File Upload

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-24809?
CVE-2024-24809 is a high vulnerability published on April 10, 2024. Traccar is an open source GPS tracking system. Versions prior to 6.0 are vulnerable to path traversal and unrestricted upload of file with dangerous type. Since the system allows registration by default, attackers can acquire ordinary user permissions by registering an account and exploit this…
When was CVE-2024-24809 disclosed?
CVE-2024-24809 was first published in the National Vulnerability Database on April 10, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-24809 actively exploited?
CVE-2024-24809 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-24809?
CVE-2024-24809 has a CVSS v3 base score of 8.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-24809?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-24809, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-24809

Explore →

Is Your Infrastructure Affected by CVE-2024-24809?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs