parse-community parse-server up to 9.5.0-alpha.9 graphQLPublictrospection authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in parse-community parse-server up to 9.5.0-alpha.9. This affects an unknown part of the component graphQLPublictrospection. The manipulation results in authorization. This vulnerability is reported as CVE-2026-30854. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in parse-community parse-server up to 9.5.0-alpha.9. It has been classified as problematic. Affected is an unknown function of the component graphQLPublictrospection. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality. CVE summarizes:
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.3.1-alpha.3 to before version 9.5.0-alpha.10, when graphQLPublicIntrospection is disabled, __type queries nested inside inline fragments (e.g. ... on Query { __type(name:"User") { name } }) bypass the introspection control, allowing unauthenticated users to perform type reconnaissance. __schema introspection is not affected. This issue has been patched in version 9.5.0-alpha.10.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-30854 since 03/05/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.
Upgrading to version 9.5.0-alpha.10 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-10171). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 9.5.0-alpha.0
- 9.5.0-alpha.1
- 9.5.0-alpha.2
- 9.5.0-alpha.3
- 9.5.0-alpha.4
- 9.5.0-alpha.5
- 9.5.0-alpha.6
- 9.5.0-alpha.7
- 9.5.0-alpha.8
- 9.5.0-alpha.9
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: parse-server 9.5.0-alpha.10
Timeline
03/05/2026 CVE reserved03/07/2026 Advisory disclosed
03/07/2026 VulDB entry created
03/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-30854 (🔒)
GCVE (CVE): GCVE-0-2026-30854
GCVE (VulDB): GCVE-100-349692
EUVD: 🔒
Entry
Created: 03/07/2026 18:09Updated: 03/12/2026 14:39
Changes: 03/07/2026 18:09 (66), 03/07/2026 20:55 (1), 03/12/2026 14:39 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.