parse-server
Affected
- introduced
0, fixed8.6.9(semver)
Fixed versions
8.6.9
Fix
- Fixed version
8.6.9npm install [email protected]
Advisory
Also known as: BIT-parse-2026-30850, CVE-2026-30850
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 overriding the route with a middleware that rejects all requests:
// Add before mounting Parse Server
app.get('/parse/files/:appId/metadata/:filename', (req, res) => {
res.status(403).json({ error: 'Forbidden' });
});
Adjust the path prefix (/parse) to match your mountPath.
References
Medium Basis: The source's own band: MODERATE
0, fixed 8.6.9 (semver)8.6.9
8.6.9npm install [email protected]9.0.0-alpha.1, fixed 9.5.0-alpha.9 (semver)9.5.0-alpha.9
9.5.0-alpha.9npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0