CVE-2024-31214

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 18% (97th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Weaponized

Also known asEUVD-2024-29114 (ENISA EUVD)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 18%CVSS: 9.6Exploit: MetasploitExposed services: Not assessed

A fix is available — apply it.

Traccar is an open source GPS tracking system. Traccar versions 5.1 through 5.12 allow arbitrary files to be uploaded through the device image upload API. Attackers have full control over the file contents, full control over the directory where the file is stored, full control over the file extension, and partial control over the file name. While it's not for an attacker to overwrite an existing file, an attacker can create new files with certain names and attacker-controlled extensions anywhere on the file system. This can potentially lead to remote code execution, XSS, DOS, etc. The default install of Traccar makes this vulnerability more severe. Self-registration is enabled by default, allowing anyone to create an account to exploit this vulnerability. Traccar also runs by default with root/system privileges, allowing files to be placed anywhere on the file system. Version 6.0 contains a fix for the issue. One may also turn off self-registration by default, as that would make most vulnerabilities in the application much harder to exploit by default and reduce the severity considerably.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
69
EG Risk 69/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
18%
EPSS %ILE
97th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
18% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 10, 2024

Last Modified

January 9, 2025

Advisory Details (4)

Auto-updated Oct 2, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Unrestricted file upload vulnerability in device image upload could lead to remote code execution · Advisory · traccar/traccar · GitHub

https://github.com/traccar/traccar/security/advisories/GHSA-3gxq-f2qj-c8v9
GitHub commit Patch Available

commit 3fbdcd81566b (traccar/traccar)

Patch available: traccar/traccar v6.6 (contains commit 3fbdcd81566b)

https://github.com/traccar/traccar/commit/3fbdcd81566bc72e319ec05c77cf8a4120b87b8f
Web page

traccar/src/main/java/org/traccar/api/resource/DeviceResource.java at v5.12 · traccar/traccar · GitHub

https://github.com/traccar/traccar/blob/v5.12/src/main/java/org/traccar/api/resource/DeviceResource.java#L191
Web page

traccar/src/main/java/org/traccar/model/Device.java at master · traccar/traccar · GitHub

https://github.com/traccar/traccar/blob/master/src/main/java/org/traccar/model/Device.java#L56

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 245 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:47 UTCEPSS rescoreEPSS 18% · 97th percentile
  2. 2026-11-12 22:49 UTCEchelonGraph re-scored
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 18% · 97th percentile
  4. 2026-11-12 00:35 UTCEchelonGraph re-scored
  5. 2026-11-11 16:34 UTCEPSS rescoreEPSS 18% · 97th percentile
  6. 2026-11-11 02:24 UTCEchelonGraph re-scored
  7. 2026-11-10 16:38 UTCEPSS rescoreEPSS 18% · 97th percentile
  8. 2026-11-10 04:02 UTCEchelonGraph re-scored
  9. 2026-11-09 16:31 UTCEPSS rescoreEPSS 18% · 97th percentile
  10. 2026-11-09 05:51 UTCEchelonGraph re-scored
  11. 2026-11-08 16:36 UTCEPSS rescoreEPSS 18% · 97th percentile
  12. 2026-11-08 07:40 UTCEchelonGraph re-scored
  13. 2026-11-07 16:35 UTCEPSS rescoreEPSS 18% · 97th percentile
  14. 2026-11-07 09:29 UTCEchelonGraph re-scored
  15. 2026-11-06 16:32 UTCEPSS rescoreEPSS 18% · 97th percentile
  16. 2026-11-06 11:18 UTCEchelonGraph re-scored
  17. 2026-11-05 16:34 UTCEPSS rescoreEPSS 18% · 97th percentile
  18. 2026-11-05 13:07 UTCEchelonGraph re-scored
  19. 2026-11-04 23:55 UTCOSV refresh
  20. 2026-11-04 16:32 UTCEPSS rescoreEPSS 18% · 97th percentile
  21. 2026-11-04 14:54 UTCEchelonGraph re-scored
  22. 2026-11-03 16:42 UTCEPSS rescoreEPSS 18% · 97th percentile
  23. 2026-11-02 18:21 UTCEchelonGraph re-scored
  24. 2026-11-02 16:40 UTCEPSS rescoreEPSS 18% · 97th percentile
  25. 2026-11-01 20:09 UTCEchelonGraph re-scored
Show 72 more
  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 18% · 97th percentile
  2. 2026-10-31 21:58 UTCEchelonGraph re-scored
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  4. 2026-10-30 23:46 UTCEchelonGraph re-scored
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 18% · 97th percentile
  6. 2026-10-30 01:35 UTCEchelonGraph re-scored
  7. 2026-10-29 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  8. 2026-10-29 03:24 UTCEchelonGraph re-scored
  9. 2026-10-28 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  10. 2026-10-28 05:13 UTCEchelonGraph re-scored
  11. 2026-10-27 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  12. 2026-10-27 07:02 UTCEchelonGraph re-scored
  13. 2026-10-26 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  14. 2026-10-25 17:12 UTCEchelonGraph re-scored
  15. 2026-10-25 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  16. 2026-10-25 07:32 UTCEchelonGraph re-scored
  17. 2026-10-24 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  18. 2026-10-24 09:21 UTCEchelonGraph re-scored
  19. 2026-10-23 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  20. 2026-10-23 11:09 UTCEchelonGraph re-scored
  21. 2026-10-22 16:31 UTCEPSS rescoreEPSS 18% · 97th percentile
  22. 2026-10-22 12:58 UTCEchelonGraph re-scored
  23. 2026-10-21 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  24. 2026-10-21 14:46 UTCEchelonGraph re-scored
  25. 2026-10-20 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  26. 2026-10-19 17:04 UTCEchelonGraph re-scored
  27. 2026-10-19 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  28. 2026-10-18 18:51 UTCEchelonGraph re-scored
  29. 2026-10-18 16:29 UTCEPSS rescoreEPSS 18% · 97th percentile
  30. 2026-10-18 07:18 UTCEchelonGraph re-scored
  31. 2026-10-17 20:38 UTCEchelonGraph re-scored
  32. 2026-10-17 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  33. 2026-10-16 22:25 UTCEchelonGraph re-scored
  34. 2026-10-16 16:36 UTCEPSS rescoreEPSS 18% · 97th percentile
  35. 2026-10-15 19:06 UTCEchelonGraph re-scored
  36. 2026-10-15 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  37. 2026-10-14 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  38. 2026-10-14 12:49 UTCEchelonGraph re-scored
  39. 2026-10-13 16:30 UTCEPSS rescoreEPSS 18% · 97th percentile
  40. 2026-10-12 17:56 UTCEchelonGraph re-scored
  41. 2026-10-12 16:31 UTCEPSS rescoreEPSS 18% · 97th percentile
  42. 2026-10-11 21:20 UTCEchelonGraph re-scored
  43. 2026-10-11 16:14 UTCEchelonGraph re-scored
  44. 2026-10-11 13:46 UTCEPSS rescoreEPSS 18% · 97th percentile
  45. 2026-10-11 13:36 UTCOSV refresh
  46. 2026-10-10 19:58 UTCEPSS rescoreEPSS 18% · 97th percentile
  47. 2026-10-09 20:05 UTCEPSS rescoreEPSS 18% · 97th percentile
  48. 2026-10-08 17:07 UTCEPSS rescoreEPSS 18% · 97th percentile
  49. 2026-10-07 23:46 UTCEPSS rescoreEPSS 18% · 97th percentile
  50. 2026-10-06 15:15 UTCEPSS rescoreEPSS 18% · 97th percentile
  51. 2026-10-05 17:41 UTCEPSS rescoreEPSS 18% · 97th percentile
  52. 2026-10-03 14:24 UTCEPSS rescoreEPSS 18% · 97th percentile
  53. 2026-10-01 19:48 UTCEPSS rescoreEPSS 18% · 97th percentile
  54. 2026-09-30 19:42 UTCEchelonGraph re-scored
  55. 2026-09-30 15:01 UTCEPSS rescoreEPSS 18% · 97th percentile
  56. 2026-09-29 15:17 UTCEPSS rescoreEPSS 18% · 97th percentile
  57. 2026-09-28 13:49 UTCEPSS rescoreEPSS 18% · 97th percentile
  58. 2026-09-27 13:43 UTCEPSS rescoreEPSS 18% · 97th percentile
  59. 2026-09-26 15:57 UTCEPSS rescoreEPSS 18% · 97th percentile
  60. 2026-09-26 00:23 UTCEPSS rescoreEPSS 18% · 97th percentile
  61. 2026-09-24 14:01 UTCEPSS rescoreEPSS 18% · 97th percentile
  62. 2026-09-23 13:46 UTCEPSS rescoreEPSS 18% · 97th percentile
  63. 2026-09-22 14:46 UTCEPSS rescoreEPSS 18% · 97th percentile
  64. 2026-09-22 01:45 UTCOSV refresh
  65. 2026-09-19 15:40 UTCEPSS rescoreEPSS 18% · 97th percentile
  66. 2026-09-18 19:26 UTCEPSS rescoreEPSS 18% · 97th percentile
  67. 2026-09-16 14:06 UTCEPSS rescoreEPSS 18% · 96th percentile
  68. 2026-09-15 03:08 UTCEPSS rescoreEPSS 18% · 96th percentile
  69. 2026-09-13 16:45 UTCEPSS rescoreEPSS 18% · 96th percentile
  70. 2026-09-12 14:59 UTCEPSS rescoreEPSS 18% · 96th percentile
  71. 2026-09-11 14:51 UTCEPSS rescoreEPSS 18% · 96th percentile
  72. 2026-09-11 09:35 UTCEPSS rescoreEPSS 18% · 96th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). Defenders should treat patch urgency accordingly.

  • Metasploitexploit/linux/http/traccar_rce_upload✓ verified
    Published Sep 23, 2024

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

    Open source ↗

Frequently asked(5)

What is CVE-2024-31214?
CVE-2024-31214 is a critical-severity vulnerability; its CVE record was published on April 10, 2024. Traccar is an open source GPS tracking system. Traccar versions 5.1 through 5.12 allow arbitrary files to be uploaded through the device image upload API. Attackers have full control over the file contents, full control over the directory where the file is stored, full control over the file…
When was the CVE record for CVE-2024-31214 published?
The CVE record for CVE-2024-31214 was published on April 10, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 9, 2025; the record at its source may have been updated since.
Is CVE-2024-31214 actively exploited?
CVE-2024-31214 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 18% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-31214?
CVE-2024-31214 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2024-31214?
A fix for CVE-2024-31214 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-31214?

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