Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as client with read access to owning class
-
ExploitSend $relatedTo query with operator instead of objectId
-
ImpactBypass owning-object ACL check, disclose linked readable objects
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Query language parameterization
|
| Exploitation Conditions | Requires an authenticated client (PR:L) that already holds read access to at least one object of the owning class, and a target class that exposes a Relation field queried via $relatedTo. Exploitation consists of supplying a query operator (non-string value) in place of the owning-object objectId - including when nested inside $or, $and, or $nor - to bypass the owning-object ACL check added for GHSA-wmwx-jr2p-4j4r. Limiting factors: only objects the attacker can already read are returned (so this discloses cross-ACL linkage/relationship membership, not the contents of unreadable owning objects); impact is read-only (no integrity or availability effect); and it is confined to applications that use Relation fields and expose them to query. The workaround is a beforeFind trigger on relation-queried classes that rejects $relatedTo queries whose owning objectId is not a string; the complete fix is updating to a patched version. |
| Impact | This is a moderate, low-urgency information-disclosure flaw rather than a top priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) with vulnerable-system confidentiality only (VC:L, VI:N, VA:N) and a base score of 5.3 describes a network-reachable but authenticated issue with limited, read-only impact - consistent with the description, which requires a client that already has read access to at least one object of the owning class and only leaks the linkage of objects the attacker could already read. The signals align rather than conflict: EPSS is low (0.25%, 17th percentile), the CVE is NOT on CISA KEV, and the CISA SSVC framework records Exploitation: none, Automatable: no, Technical Impact: partial. The vuln.today decision label is 'this_month,' indicating a patch-in-normal-cycle priority, not an emergency. There are no indications of active exploitation or weaponization. In short, this is a legitimate but bounded ACL-bypass/information-disclosure bug (a regression around the owning-object authorization previously added for GHSA-wmwx-jr2p-4j4r), appropriate to remediate on a routine patch cadence rather than as a crisis. |
| Exploit ScenarioDerived | An authenticated low-privilege client of a Parse Server application that holds read access to at least one object of a class exposing a Relation field sends a $relatedTo relation query in which the owning-object reference is a query operator rather than a concrete objectId. Because the owning-object ACL check is bypassed, the server returns which readable objects are linked to owning objects the attacker is not permitted to read, disclosing relationship/linkage information across ACL boundaries. No public exploit identified at time of analysis; a vendor (VulnCheck) and GHSA advisory describe the mechanism but no verified working exploit code is provided. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Parse Server's $relatedTo relation query does not validate the owning object reference, so an authenticated client can substitute a query operator for the object ID and slip past the owning-object ACL check introduced for GHSA-wmwx-jr2p-4j4r. The result is a limited information disclosure: the attacker learns which objects they can already read are linked to owning objects they are not permitted to read, in deployments that expose Relation fields to queries. Severity is moderate (CVSS 5.3, PR:L, confidentiality-only), EPSS is low at 0.25% (17th percentile), there is no CISA KEV listing, and no public exploit has been identified at time of analysis.
RemediationAI
Upgrade to a patched release: Parse Server 8.6.105 for the 8.x line (PR https://github.com/parse-community/parse-server/pull/10784) or 9.10.5-alpha.6 for the 9.x line (PR https://github.com/parse-community/parse-server/pull/10783), noting that the 9.x fix is published as a pre-release alpha, so teams tracking stable 9.x should confirm the next stable release containing it before upgrading. Where upgrading is not immediately possible, the vendor workaround is to add a beforeFind trigger to every class queried through a Relation field that rejects $relatedTo queries whose owning objectId is not a string, including when nested in $or, $and or $nor; the cost is extra Cloud Code execution on those query paths and the need to reimplement the check for each relation-backed class, and the trigger must be written carefully or it will itself be bypassed by nested query shapes. The workaround is only a stopgap - the advisory treats the validation added in the patched versions as the complete fix - and because exploitation requires an authenticated client with read access to at least one object of the owning class, restricting Class Level Permissions and reviewing which roles can read relation-bearing classes reduces exposure in the interim. Advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-58m4-cqvw-4vgh.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Parse Server is the open-source Node.js backend for the Parse Platform, exposing a REST/GraphQL API over MongoDB or PostgreSQL where classes carry ACLs and objects can be linked through Relation fields. A relational lookup is expressed with the $relatedTo query constraint, which normally takes an owning object reference (including its objectId) plus a relation key; the server resolves the relation and returns the linked objects. This flaw is CWE-943 (improper neutralization of special elements in data query logic - the NoSQL-injection class): because the owning object reference and relation key are not validated as strings, an attacker can pass a query operator where the objectId is expected, including when nested inside $or, $and or $nor, and the owning-object authorization check is bypassed. The upstream fix in PR #10783 (9.x) and PR #10784 (8.x) validates both the owning object reference and the relation key and rejects queries whose owning reference is not a string. The trigger conditions and the exact operator semantics beyond the non-string rejection are not described in the available sources.
Know when Parse Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable API but requires an authenticated client with read access to one owning-class object (PR:L); limited read-only disclosure of linkage data gives C:L with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
Parse Server before 8.6.105 and 9.0.0 before 9.10.5-alpha.6 does not validate the owning object reference in $relatedTo relation queries, so supplying a query operator instead of an object ID bypasses the owning-object ACL check. A client with read access to at least one object of the owning class can disclose which readable objects are linked to owning objects it cannot read.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
NoSQL injection exploits databases that don't use traditional SQL syntax-like MongoDB, CouchDB, or Redis-by manipulating queries through unsanitized user input.
More in Parse Server
View allParse Server is an open source http web server backend. Rated critical severity (CVSS 10.0), this vulnerability is remot
Unauthenticated query injection in Parse Server before 9.6.0-alpha.12/8.6.38. PoC available.
Parse Server has an incorrect authorization vulnerability enabling unauthorized data access across applications.
### Impact Parse Server's built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all
Parse Server has a CVSS 10.0 access control vulnerability enabling complete bypass of all data access restrictions.
parse-server is a Parse Server for Node.js / Express. Rated critical severity (CVSS 10.0), this vulnerability is remotel
Authentication bypass in Parse Server allows unauthenticated access to protected API endpoints. Parse Server is a popula
SQL injection in Parse Server before 9.6.0-alpha.2/8.6.28.
SQL injection in Parse Server before 9.6.0-alpha.5/8.6.31. Third Parse Server SQLi.
SQL injection in Parse Server before 9.6.0-alpha.5/8.6.31.
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Rated critical s
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Rated critical s
EUVD-2026-110509
GHSA-mfg3-66fp-4xc4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB