CVEvulnerability
CVE-2026-30938
6.9 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-03-10
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 4.0 ([email protected])
- 6.9 MEDIUM — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- CVSS 3.1 ([email protected])
- 5.3 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses
- CWE-693
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 8.6.12 and 9.5.1-alpha.1, the requestKeywordDenylist security control can be bypassed by placing any nested object or array before a prohibited keyword in the request payload. This is caused by a logic bug that stops scanning sibling keys after encountering the first nested value. Any custom requestKeywordDenylist entries configured by the developer are equally by-passable using the same technique. All Parse Server deployments are affected. The requestKeywordDenylist is enabled by default. This vulnerability is fixed in 8.6.12 and 9.5.1-alpha.1. Use a Cloud Code beforeSave trigger to validate incoming data for prohibited keywords across all classes.
Affected configurations
• parseplatform parse-server (< 8.6.12)
• parseplatform parse-server (>= 9.0.0 < 9.5.1)
Related
Weakness · CWE (1)
- CWE-693 Protection Mechanism Failure weakness
References
- https://github.com/parse-community/parse-server/releases/tag/8.6.12 Product, Release Notes
- https://github.com/parse-community/parse-server/releases/tag/9.5.1-alpha.1 Product, Release Notes
- https://github.com/parse-community/parse-server/security/advisories/GHSA-q342-9w2p-57fp Mitigation, Patch, Vendor Advisory