CVE-2023-36475
Parseplatform Parse-Server ≤ 5.5.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-36475 is a critical-severity Prototype Pollution (CWE-1321) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 13% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Parse Server is an open source backend framework that runs on Node.js and connects to MongoDB. CVE-2023-36475 is a prototype-pollution vulnerability (CWE-1321) present in versions prior to 5.5.2 and 6.2.1. An attacker-supplied payload can reach a sink inside the MongoDB BSON parser, allowing the pollution to be escalated into arbitrary code execution on the server.
Because the flaw is reachable over the network with no authentication or user interaction required, any remote attacker who can send requests to a Parse Server instance can achieve full remote code execution, resulting in complete compromise of the confidentiality, integrity, and availability of the affected service.
Patches addressing the issue were released in Parse Server versions 5.5.2 and 6.2.1; the corresponding commits and release notes are available in the project repository.
EPSS for the CVE rose from a low baseline to a peak of 0.1670 on 2025-01-22 before receding to the current value of 0.0983, indicating a measurable increase in observed exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1678
Vulnerability Data
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 5.5.2 and 6.2.1, an attacker can use a prototype pollution sink to trigger a remote code execution through the…
more
MongoDB BSON parser. A patch is available in versions 5.5.2 and 6.2.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.3.6
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches prototype-pollution flaws before release.
Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.
Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.
Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.
Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.
Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.