# CVE-2026-120427: MrDoc through 1.1.1 Missing Authorization via get_doctemp Template Read


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-3j38-ccjp-5wfv

## What is CVE-2026-120427?

CVE-2026-120427 is a medium-severity vulnerability in zmister2016 MrDoc, published on 2 Nov 2026. 

### Official description

MrDoc through 1.1.1 contains a missing authorization vulnerability in the get_doctemp view that allows authenticated users to read other users' document templates. Attackers can enumerate the sequential doctemp_id POST parameter to retrieve the private template content of every user on the instance.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-120427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120427 is a medium-severity vulnerability in zmister2016 MrDoc, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120427 exists.

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

## Sources

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

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