# CVE-2026-109177: MoguBlog through 6.2 Broken Access Control via networkDisk moveFile and edit

> Authenticated administrators can move or rename other administrators' files due to missing ownership checks in network disk operations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-487q-jr6j-w878

## What is CVE-2026-109177?

CVE-2026-109177 is a medium-severity missing authorization vulnerability in moxi624 MoguBlog, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MoguBlog through 6.2 contains a broken access control vulnerability that allows authenticated administrators to move or rename other administrators' network-disk files by supplying their file paths. Attackers can send crafted requests to POST /networkDisk/moveFile, batchMoveFile, or edit, which update rows without admin_uid checks, relocating or renaming other users' files and folders.

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

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


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

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

## Is CVE-2026-109177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109177 is a medium-severity missing authorization vulnerability in moxi624 MoguBlog, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109177 exists.

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

## Sources

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

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