CVE-2024-47183

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

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

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. If the Parse Server option allowCustomObjectId: true is set, an attacker that is allowed to create a new user can set a custom object ID for that new user that exploits the vulnerability and acquires privileges of a specific role. This vulnerability is fixed in 6.5.9 and 7.3.0.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

October 4, 2024

Last Modified

February 25, 2026

Advisory Details (5)

Auto-updated Sep 11, 2026
Patch available. Sources: github_pr, github, github_commit.
github Patch Available

Custom object ID allows to acquire role privileges · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-8xq9-g7ch-35hg
github_pr

fix: Custom object ID allows to acquire role privileges (GHSA-8xq9-g7ch-35hg)

Fix merged in parse-community/parse-server PR #9318 on 2024-10-03 — awaiting tagged release

https://github.com/parse-community/parse-server/pull/9318
github_pr Patch Available

fix: Custom object ID allows to acquire role privileges (GHSA-8xq9-g7ch-35hg)

Patch available: parse-community/parse-server 9.9.1-alpha.11 (PR #9317 merged 2024-10-03)

https://github.com/parse-community/parse-server/pull/9317
github_commit

commit 1bfbccf9ee7e (parse-community/parse-server)

Fix landed in parse-community/parse-server commit 1bfbccf9ee7e — awaiting tagged release

https://github.com/parse-community/parse-server/commit/1bfbccf9ee7ea77533b2b2aa7c4c69f3bd35e66f
github_commit Patch Available

commit 13ee52f0d19e (parse-community/parse-server)

Patch available: parse-community/parse-server 9.9.1-alpha.11 (contains commit 13ee52f0d19e)

https://github.com/parse-community/parse-server/commit/13ee52f0d19ef3a3524b3d79aea100e587eb3cfc

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
parse-server—7.3.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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.

Showing the most recent 100 of 165 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-47183?
CVE-2024-47183 is a high vulnerability published on October 4, 2024. Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. If the Parse Server option allowCustomObjectId: true is set, an attacker that is allowed to create a new user can set a custom object ID for that new user that exploits the vulnerability and…
When was CVE-2024-47183 disclosed?
CVE-2024-47183 was first published in the National Vulnerability Database on October 4, 2024, with the most recent update on February 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-47183 actively exploited?
CVE-2024-47183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.4% of all scored CVEs.
What is the CVSS score of CVE-2024-47183?
CVE-2024-47183 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2024-47183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-47183, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-47183

Explore →

Is Your Infrastructure Affected by CVE-2024-47183?

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

Start Free Scan →Browse All CVEs