# CVE-2026-120448: DoraCMS through 3.1.0 Mass Assignment via API Key Update Endpoint


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-x998-w6fg-m92w

## What is CVE-2026-120448?

CVE-2026-120448 is a high-severity vulnerability in doramart DoraCMS, published on 2 Nov 2026. 

### Official description

DoraCMS through 3.1.0 contains a mass assignment vulnerability in the PUT /api/v1/user/api-keys/:id endpoint that allows authenticated low-privileged users to rebind their API key to another user's account. Attackers can set the userId field on their own key to a victim's id, then act as that victim to modify profiles and publish or delete content.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-120448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120448 is a high-severity vulnerability in doramart DoraCMS, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120448 exists.

Affected product: doramart DoraCMS. 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-120448/ (Markdown: https://insights.sbomify.com/CVE-2026-120448/index.md)
```

## Sources

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

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