# CVE-2026-89261: MoguBlog through 6.2 Missing Authentication for Elasticsearch Index Management Endpoints

> Remote attackers can delete or alter the blog search index via unauthenticated Elasticsearch endpoints, disrupting search functionality.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-4j85-4728-jr5q

## What is CVE-2026-89261?

CVE-2026-89261 is a medium-severity missing authorization vulnerability in moxi624 MoguBlog, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MoguBlog through 6.2 exposes Elasticsearch index management endpoints in the mogu_search service without authentication, allowing remote attackers to delete, recreate, or alter the blog search index. Attackers can invoke POST endpoints to wipe the entire search index, delete specific documents, or inject malicious index entries, causing search functionality to return incorrect or no results.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-89261 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89261 is a medium-severity missing authorization vulnerability in moxi624 MoguBlog, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89261 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-89261/ (Markdown: https://insights.sbomify.com/CVE-2026-89261/index.md)
```

## Sources

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

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