# CVE-2026-89265: MoguBlog through 6.2 Missing Authorization on the Admin getPictureSortByUid Endpoint

> Authenticated users can bypass authorization checks to retrieve restricted image-category metadata via the getPictureSortByUid endpoint.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jgmr-fg2f-g83q

## What is CVE-2026-89265?

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

### Official description

MoguBlog through 6.2 contains an authorization bypass vulnerability in the POST /pictureSort/getPictureSortByUid endpoint, which omits the @AuthorityVerify annotation required to enforce role-based permissions. Authenticated back-office users without image-category permissions can supply a category uid to retrieve restricted image-category records including metadata such as name, cover file uid, sort order and timestamps.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-89265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89265 is a medium-severity missing authorization vulnerability in moxi624 MoguBlog, published on 11 Sep 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-89265 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-89265/ (Markdown: https://insights.sbomify.com/CVE-2026-89265/index.md)
```

## Sources

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

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