CVE-2026-30850
published 2026-03-07CVE-2026-30850: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.9 and 9.5.0-alpha.9, the file…
PriorityP336medium5.9CVSS 3.1
AVNACHPRNUINSUCHINAN
EPSS
0.29%
21.1th percentile
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.9 and 9.5.0-alpha.9, the file metadata endpoint (GET /files/:appId/metadata/:filename) does not enforce beforeFind / afterFind file triggers. When these triggers are used as access-control gates, the metadata endpoint bypasses them entirely, allowing unauthorized access to file metadata. This issue has been patched in versions 8.6.9 and 9.5.0-alpha.9.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| parse-community | parse-server | < 8.6.9 | 8.6.9 |
| parse-community | parse-server | < 9.5.0-alpha.9 | 9.5.0-alpha.9 |
| parse-community | parse-server | >= 0 < 8.6.9 | 8.6.9 |
| parse-community | parse-server | >= 9.0.0-alpha.1 < 9.5.0-alpha.9 | 9.5.0-alpha.9 |
| parseplatform | parse-server | < 8.6.9 | 8.6.9 |
| parseplatform | parse-server | — | — |
| parseplatform | parse-server | >= 9.0.0 < 9.5.0 | 9.5.0 |
CVSS provenance
nvdv3.15.9MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv4.06.3MEDIUMCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/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
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
osv·2026-03-09
CVE-2026-30850 [MEDIUM] Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
### Impact
The file metadata endpoint (GET `/files/:appId/metadata/:filename`) does not enforce `beforeFind` / `afterFind` file triggers. When these triggers are used as access-control gates, the metadata endpoint bypasses them entirely, allowing unauthorized access to file metadata.
This affects any deployment that relies on `Parse.Cloud.beforeFind(Parse.File, ...)` to restrict file access. Only file metadata (user-defined key-value pairs set via addMetadata) is exposed; file content remains protected.
### Patches
The metadata handler now runs `beforeFind` and `afterFind` triggers and returns HTTP 403 when a trigger denies access.
### Workarounds
Disable the `metadata` endpoint by overrid
GHSA
Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
ghsa·2026-03-09
CVE-2026-30850 [MEDIUM] CWE-862 Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
Parse Server: File metadata endpoint bypasses `beforeFind` / `afterFind` trigger authorization
### Impact
The file metadata endpoint (GET `/files/:appId/metadata/:filename`) does not enforce `beforeFind` / `afterFind` file triggers. When these triggers are used as access-control gates, the metadata endpoint bypasses them entirely, allowing unauthorized access to file metadata.
This affects any deployment that relies on `Parse.Cloud.beforeFind(Parse.File, ...)` to restrict file access. Only file metadata (user-defined key-value pairs set via addMetadata) is exposed; file content remains protected.
### Patches
The metadata handler now runs `beforeFind` and `afterFind` triggers and returns HTTP 403 when a trigger denies access.
### Workarounds
Disable the `metadata` endpoint by overrid
No detection rules found.
No public exploits indexed.
2026-03-07
Published