# CVE-2026-119707: SonicJS through 3.0.0 Missing Authorization in Content Write API


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-4392-9339-gxp5

## What is CVE-2026-119707?

CVE-2026-119707 is a high-severity vulnerability in SonicJs-Org sonicjs, published on 30 Oct 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-119707?


## How do I fix CVE-2026-119707?

No fix has been published for CVE-2026-119707 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119707 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119707 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119707 and fix it if it is affected.

What it is: CVE-2026-119707 is a high-severity vulnerability in SonicJs-Org sonicjs, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119707 exists.

Affected product: SonicJs-Org sonicjs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119707/ (Markdown: https://insights.sbomify.com/CVE-2026-119707/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119707
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119707
- OSV: https://osv.dev/vulnerability/CVE-2026-119707

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119707/
Summaries are generated and may contain mistakes; the official description above is the record.