Authenticated code execution via post-trigger denylist bypass
Published Nov 10, 2022 · Updated Apr 23, 2025
Prototype pollution in Parse Server before 4.10.19 and 5.0.0 through 5.3.1 allows remote authenticated users to execute code. RestWrite scans request data for denied keys before Cloud Code runs, but affected builds do not rescan data returned by a trigger or webhook before saving it. Exploitation requires high-privilege API access, requestKeywordDenylist configuration, and an active Cloud Code trigger or webhook; code runs as the service account.
Summary
What happened
Prototype pollution in Parse Server before 4.10.19 and 5.0.0 through 5.3.1 allows remote authenticated users to execute code. RestWrite scans request data for denied keys before Cloud Code runs, but affected builds do not rescan data returned by a trigger or webhook before saving it. Exploitation requires high-privilege API access, requestKeywordDenylist configuration, and an active Cloud Code trigger or webhook; code runs as the service account.
The record
- CVE
- CVE-2022-41878
- Published
- Nov 10, 2022
- Updated
- Apr 23, 2025
- Vendor
- Parse Platform
- Product
- Parse Server
- Classifications
- CWE-1321, CWE-74, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 10, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.10.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo