CVE-2024-47183

Workarounds

• Disable custom object IDs by setting allowCustomObjectId: false or not setting the option which defaults to false.
• Use a Cloud Code Trigger to validate that a new user's object ID doesn't start with the prefix role:.

References

• https://github.com/parse-community/parse-server/security/advisories/GHSA-8xq9-g7ch-35hg
• https://github.com/parse-community/parse-server/pull/9317 (fix for Parse Server 7)
• https://github.com/parse-community/parse-server/pull/9318 (fix for Parse Server 6)

If the Parse Server option allowCustomObjectId: true is set, an attacker that is allowed to create a new user can set a custom object ID for that new user that exploits the vulnerability and acquires privileges of a specific role.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2024-47183 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.5.9, 7.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

Improved validation for custom user object IDs. Session tokens for existing users with an object ID that exploits the vulnerability are now rejected.

1. What is CVE-2024-47183? CVE-2024-47183 is a high-severity incorrect authorization vulnerability in parse-server (npm), affecting versions < 6.5.9. It is fixed in 6.5.9, 7.3.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2024-47183? CVE-2024-47183 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of parse-server are affected by CVE-2024-47183? parse-server (npm) versions < 6.5.9 is affected.
4. Is there a fix for CVE-2024-47183? Yes. CVE-2024-47183 is fixed in 6.5.9, 7.3.0. Upgrade to this version or later.
5. Is CVE-2024-47183 exploitable, and should I be worried? Whether CVE-2024-47183 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47183 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47183?
   • Upgrade parse-server to 6.5.9 or later
   • Upgrade parse-server to 7.3.0 or later

Other vulnerabilities in parse-server