CVE-2023-41058: Trigger `beforeFind` not invoked in internal query pipeline in parse-server

Published Sep 4, 2023
·
Updated

Impact

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.

Patches

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.

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

Other sources

Parse Server is an open source backend server. In affected versions the Parse Cloud trigger beforeFind is not invoked in certain conditions of Parse.Query. This can pose a vulnerability for deployments where the beforeFind trigger is used as a security layer to modify the incoming query. The vulnerability has been fixed by refactoring the internal query pipeline for a more concise code structure and implementing a patch to ensure the beforeFind trigger is invoked. This fix was introduced in commit be4c7e23c6 and has been included in releases 6.2.2 and 5.5.5. Users are advised to upgrade. Users unable to upgrade should make use of parse server's security layers to manage access levels with Class-Level Permissions and Object-Level Access Control that should be used instead of custom security layers in Cloud Code triggers.

Affected Software

4 affected componentsFixes available
npm/parse-server>=6.0.0<6.2.2
6.2.2
npm/parse-server>=1.0.0<5.5.5
5.5.5
parseplatform Parse-server Node.js<5.5.5
parseplatform Parse-server Node.js>=6.0.0<6.2.2

Event History

Sep 4, 2023
CVE Published
via MITRE·10:39 PM
Data Sourced
via MITRE·10:39 PM
DescriptionSeverityWeakness
Advisory Published
10:40 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-41058?

CVE-2023-41058 is a vulnerability in Parse Server that allows a Parse Pointer to access internal classes and bypass the beforeFind query trigger.

2

What is the impact of CVE-2023-41058?

The impact of CVE-2023-41058 is that it can bypass the beforeFind query trigger, which can be a security vulnerability if the trigger is being used to modify incoming queries.

3

What is the severity of CVE-2023-41058?

CVE-2023-41058 has a severity rating of 7.5 (High).

4

How can I fix CVE-2023-41058?

To fix CVE-2023-41058, update Parse Server to version 6.2.2 or above.

5

Where can I find more information about CVE-2023-41058?

You can find more information about CVE-2023-41058 at the following references: [Reference 1](https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q), [Reference 2](https://nvd.nist.gov/vuln/detail/CVE-2023-41058), [Reference 3](https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203