CVE-2023-41058

Workarounds

There is no known workaround to prevent a Parse Pointer to be used to access internal Parse Server classes. A workaround if a beforeFind trigger is used as a security layer is to instead use the Parse Server provided security layers to manage access levels with Class-Level Permissions and Object-Level Access Control.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
• Patched in Parse Server 6.x: https://github.com/parse-community/parse-server/releases/tag/6.2.2
• Patched in Parse Server 5.x (LTS): https://github.com/parse-community/parse-server/releases/tag/5.5.5

A Parse Pointer can be used to access internal Parse Server classes. It can also be used to circumvent the beforeFind query trigger which can be an additional vulnerability for deployments where the beforeFind trigger is used as a security layer to modify an incoming query.

CVE-2023-41058 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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 (5.5.5, 6.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability was fixed by implementing a patch in the internal query pipeline to prevent a Parse Pointer to be used to access internal Parse Server classes or circumvent the beforeFind trigger.

1. What is CVE-2023-41058? CVE-2023-41058 is a high-severity security vulnerability in parse-server (npm), affecting versions >= 1.0.0, < 5.5.5. It is fixed in 5.5.5, 6.2.2.
2. How severe is CVE-2023-41058? CVE-2023-41058 has a CVSS score of 7.5 (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-2023-41058? parse-server (npm) versions >= 1.0.0, < 5.5.5 is affected.
4. Is there a fix for CVE-2023-41058? Yes. CVE-2023-41058 is fixed in 5.5.5, 6.2.2. Upgrade to this version or later.
5. Is CVE-2023-41058 exploitable, and should I be worried? Whether CVE-2023-41058 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-2023-41058 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-2023-41058?
   • Upgrade parse-server to 5.5.5 or later
   • Upgrade parse-server to 6.2.2 or later

Other vulnerabilities in parse-server