SonicJS through 3.0.0 contains a missing authorization vulnerability in the /api/:collection and /api/content write routes that only check coarse role labels. Authenticated authors or editors can use a bearer JWT or API key to create, modify, publish, or soft-delete other users' documents, bypassing document ACLs and administrator deny overrides.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/SonicJs-Org/sonicjs/pull/1147 patch, issue-tracking
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.1 · sonicjs-orgNVD modified 2026-10-30 15:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/SonicJs-Org/sonicjs/issues/1125 issue-tracking
- https://github.com/SonicJs-Org/sonicjs product
- https://github.com/SonicJs-Org/sonicjs/blob/v3.0.0/packages/core/src/routes/api.ts#L1296 technical-description
- https://github.com/SonicJs-Org/sonicjs/pull/1147 patch, issue-tracking
- https://hackmd.io/@hieuPenguinnn/sonicjs-content-api-write-acl-bypass third-party-advisory
- https://www.vulncheck.com/advisories/sonicjs-through-3.0.0-missing-authorization-in-content-write-api third-party-advisory