CVE-2023-41058

Trigger `beforeFind` not invoked in internal query pipeline in parse-server

HIGH

7.5

CVSS Score

Published: September 4, 2023 at 10:39 PM UTC

Updated: June 17, 2026 at 06:20 AM UTC

2 products affected across 2 vendorsParse ServerParse Server

Using parse-server by parse-community?

Get instant alerts when new vulnerabilities affect parse-server - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.8%

SSVC

No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Parse Server · Parseplatformnpm

95%

v < 5.5.56.0.0 ≤ v < 6.2.2

Affected range stops below 5.5.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.2.2, so it looks safe — our inference, not a vendor statement

Parse Server · Parse Communitynpm

60%

v < 5.5.5v < 6.2.2

Affected range stops below 5.5.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.2.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (5)

x_refsource_MISCProduct

Source: [email protected]

https://docs.parseplatform.org/parse-server/guide/#security

x_refsource_MISCPatch

Source: [email protected]

https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5

x_refsource_MISCRelease Notes

Source: [email protected]

https://github.com/parse-community/parse-server/releases/tag/5.5.5

x_refsource_MISCRelease Notes

Source: [email protected]

https://github.com/parse-community/parse-server/releases/tag/6.2.2

x_refsource_CONFIRMMitigationVendor Advisory

Source: [email protected]

https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-670

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card