CVE-2026-30947: Parse Server ha a bypass of class-level permissions in LiveQuery
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: parse-community parse-server 9.5.2-alpha.3.
Low priority for now. Upgrade to parse-community parse-server 9.5.2-alpha.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.3 and 8.6.16, class-level permissions (CLP) are not enforced for LiveQuery subscriptions. An unauthenticated or unauthorized client can subscribe to any LiveQuery-enabled class and receive real-time events for all objects, regardless of CLP restrictions. All Parse Server deployments that use LiveQuery with class-level permissions are affected. Data intended to be restricted by CLP is leaked to unauthorized subscribers in real time. This vulnerability is fixed in 9.5.2-alpha.3 and 8.6.16.
- Published
- Mar 10, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-863
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| parseplatform | parse-server | cpe:2.3:a:parseplatform:parse-server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- parseplatform parse-serverbefore 8.6.16
- parseplatform parse-server9.0.0 and later · before 9.5.2
- parseplatform parse-server9.5.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
parse-community parse-server
- >= 9.0.0 < 9.5.2-alpha.3, < 8.6.16affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | parse-server | from 9.0.0 · before 9.5.2-alpha.3 | 9.5.2-alpha.3 |
| npm | parse-server | before 8.6.16 | 8.6.16 |
Same product
parseplatform: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-24760Command Injection in Parse server55Plan
- CVE-2022-39396Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser51Plan
- CVE-2026-30966Parse Server role escalation and CLP bypass via direct `_Join` table write40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-30941Mar 10, 2026 · Parse Server has a NoSQL injection via token type in password reset and email verification endpoints34Monitor
- ← EarlierCVE-2026-30946Mar 10, 2026 · Parse Server affected by denial-of-service via unbounded query complexity in REST and GraphQL API34Monitor
- Later →CVE-2026-30948Mar 10, 2026 · Parse Server has stored cross-site scripting (XSS) via SVG file upload33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| parse-community parse-server | 9.5.2-alpha.3 · description | Vendor (CNA) |
| npm:parse-server | 8.6.16 | Package registry (OSV) |
| npm:parse-server | 9.5.2-alpha.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-309650 days apartParse Server session token exfiltration via `redirectClassNameForKey` query parameter39Monitor
- CVE-2026-3453221 days apartParse Server: Cloud function validator bypass via prototype chain traversal36Monitor
- CVE-2026-291824 days apartParse Server: Cloud Hooks and Cloud Jobs bypass `readOnlyMasterKey` write restriction34Monitor
- CVE-2026-302294 days apartParse Server: Endpoint `/loginAs` allows `readOnlyMasterKey` to gain full read and write access as any user34Monitor
- CVE-2026-3342114 days apartParse Server: LiveQuery bypasses CLP pointer permission enforcement28Monitor
- CVE-2026-308543 days apartParse Server: GraphQL `__type` introspection bypass via inline fragments when public introspection is disabled27Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.