Skip to content
Fencer Intel
critical 9.8

CVE-2022-39396 in the critical feed json

Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser

published 4y ago modified 2mo ago also BIT-parse-2022-39396 , EUVD-2022-7404 , GHSA-prm5-8g2m-24gg

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
39.4%
EPSS 39.4% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.18, and prior to 5.3.1 on the 5.X branch, are vulnerable to Remote Code Execution via prototype pollution. An attacker can use this prototype pollution sink to trigger a remote code execution through the MongoDB BSON parser. This issue is patched in version 5.3.1 and in 4.10.18. There are no known workarounds.

Patch / fix

  • npm parse-server 4.10.18, 5.3.1
  • bitnami parse 4.10.18, 5.3.1
  • parseplatform parse-server 4.10.18, 5.3.1

Is CVE-2022-39396 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

39.35% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm parse-server
<4.10.18
>=5.0.0, <5.3.1
4.10.18
5.3.1
bitnami parse
<4.10.18
>=5.0.0, <5.3.1
4.10.18
5.3.1

Affected products

  • parse-community parse-server

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel 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.