# CVE-2026-89260: MoguBlog through 6.2 XML External Entity Injection in the Unauthenticated WeChat Callback Endpoint


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-92wh-xp96-v6mj

## What is CVE-2026-89260?

CVE-2026-89260 is a high-severity vulnerability in moxi624 MoguBlog, published on 11 Sep 2026. 

### Official description

MoguBlog through 6.2 contains an XML external entity injection vulnerability in the WeChat callback handler at POST /wechat/wechatCheck. The WechatRestApi.index() method passes the raw request body to SignUtil.xmlToMap(), which uses an unhardened dom4j SAXReader without DTD or external-entity restrictions. Unauthenticated remote attackers can submit DOCTYPE declarations with external parameter entities to read arbitrary local files or trigger outbound HTTP requests, with resolved entities reflected in error responses.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2026-89260 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89260 is a high-severity vulnerability in moxi624 MoguBlog, published on 11 Sep 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89260 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-89260/ (Markdown: https://insights.sbomify.com/CVE-2026-89260/index.md)
```

## Sources

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

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