CVE-2023-41058 json
Trigger `beforeFind` not invoked in internal query pipeline in parse-server
published 3y ago modified 2mo ago also BIT-parse-2023-41058 , EUVD-2023-2492 , GHSA-fcv6-fg5r-jm9q
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm parse-server 5.5.5, 6.2.2
- bitnami parse 5.5.5, 6.2.2
- parseplatform parse-server 5.5.5, 6.2.2
Is CVE-2023-41058 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | >=1.0.0, <5.5.5 >=6.0.0, <6.2.2 |
5.5.5 6.2.2 |
| bitnami | parse | <5.5.5 >=6.0.0, <6.2.2 |
5.5.5 6.2.2 |
Affected products
- parse-community parse-server
Classification
- Weakness
-
- CWE-670 Always-Incorrect Control Flow Implementation
References
-
github.com
/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5
web, patch
-
github.com
/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
web, mitigation, vendor-advisory, advisory
-
docs.parseplatform.org
/parse-server/guide/#security
web, product
-
github.com
/parse-community/parse-server/releases/tag/5.5.5
web, release-notes, article
-
github.com
/parse-community/parse-server/releases/tag/6.2.2
web, release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2023-41058
advisory, web
-
github.com
/parse-community/parse-server
package
Sources
- CVE List CVE-2023-41058
- GitHub Advisory GHSA-fcv6-fg5r-jm9q
- NVD CVE-2023-41058
- OSV BIT-parse-2023-41058
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.