CVE-2022-31112: parse-server - Protected fields exposed via LiveQuery
Summary
CVE-2022-31112: Protected fields exposed via LiveQuery. Affects parse-server across 2 version ranges.
< 4.10.13
>= 5.0.0, < 5.2.4
Fixed in 4.10.13 or 5.2.4, depending on the release line you run. How to fix ↓
Also tracked for
- parse · Bitnami
The same CVE-2022-31112 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
parse-server is an open-source backend framework that provides a scalable and flexible platform for building applications. It includes features such as data storage, user authentication, and push notifications. LiveQuery is a real-time subscription feature in parse-server that allows clients to receive updates in real-time when data changes in the database. However, a vulnerability has been discovered in parse-server LiveQuery where protected fields in classes are not properly removed, leading to their exposure to clients.
Vulnerability Detail
The vulnerability in parse-server LiveQuery allows protected fields in classes to be passed to the client, even though they should be hidden. This can potentially expose sensitive information that should not be accessible to clients. An attacker could exploit this vulnerability to gain unauthorized access to protected data or perform other malicious actions. The impact of this vulnerability is considered HIGH with a CVSS score of 8.2.
How To Fix
Latest published version: 9.10.5 as of 22 Oct 2026
npm install parse-server@9.10.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 4.10.134.10.13npm install parse-server@4.10.13 -
>= 5.0.0, < 5.2.45.2.4npm install parse-server@5.2.4
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If updating parse-server is not immediately feasible, a workaround is available. Developers can use the Parse.Cloud.afterLiveQueryEvent function to manually remove protected fields from the client response. This can be done by accessing the response object and removing any fields that should not be exposed to clients. Here is an example of how to implement this workaround:
Parse.Cloud.afterLiveQueryEvent((request) => {
const response = request.response;
// Remove protected fields from response
delete response.protectedField1;
delete response.protectedField2;
// Return modified response
return response;
});
Conclusion
The vulnerability in parse-server LiveQuery exposes protected fields to clients, potentially leading to unauthorized access or other malicious actions. It is crucial to update parse-server to the recommended versions or apply the provided workaround to mitigate this vulnerability. Regularly updating parse-server is essential to stay protected against known vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for parse-server →
FAQ
parse-server is an open-source backend framework that provides a scalable and flexible platform for building applications. It includes features such as data storage, user authentication, and push notifications.
LiveQuery is a real-time subscription feature in parse-server that allows clients to receive updates in real-time when data changes in the database.
The impact of this vulnerability is considered HIGH with a CVSS score of 8.2. It can potentially expose sensitive information that should not be accessible to clients, leading to unauthorized access or other malicious actions.
To fix this vulnerability, it is recommended to update parse-server to version 4.10.13 or later for versions 4.x.x, and to version 5.2.4 or later for versions 5.x.x. Updating to these versions will ensure that protected fields are properly removed from the client response in LiveQuery.
Yes, a workaround is available if updating parse-server is not immediately feasible. Developers can use the Parse.Cloud.afterLiveQueryEvent function to manually remove protected fields from the client response.
References
Related vulnerabilities
Recent vulnerabilities recorded for parse-server.
