/

CVE-2026-89260

Severity:

HIGH RISK

(7.5)

XML External Entity (CWE-611) in MoguBlog WeChat Handler

CVE-2026-89260

Deferred

Vulnerability type

Category:

XML External Entity Injection

CWE:

CWE-611

Impact:

Sensitive File Disclosure and Server-Side Request Forgery

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

MoguBlog's WeChat callback handler parses attacker-controlled XML with an unhardened SAX reader, allowing external entities to be resolved during request processing. An unauthenticated remote attacker may read local files or cause the server to make outbound HTTP requests when the callback endpoint accepts malicious XML.

Affected context

The vulnerability occurs in deployments that expose the WeChat callback endpoint at POST /wechat/wechatCheck and pass the raw request body to XML parsing logic without disabling DTD processing and external entity resolution. Risk is higher when the application process can read sensitive local files or reach internal and external network services.

Exploit preconditions

  • Attack surface: The publicly reachable WeChat callback HTTP endpoint
  • Required access: No authentication may be required when the callback handler accepts requests directly
  • Trigger point: XML parsing performed by SignUtil.xmlToMap() during callback processing
  • Why exploitation is possible: The XML parser permits DTD declarations and external entity resolution, allowing attacker-controlled document references to be processed by the server

Why this happens

The underlying bug is unsafe XML parser configuration. The callback handler supplies untrusted request content to a dom4j SAXReader without restricting DTD handling or external entities, so document structure can cause the parser to access local resources or initiate network connections.

This behavior maps to CWE-611: Improper Restriction of XML External Entity Reference, where XML input can influence resource resolution beyond the intended application data model.

Potential impact

  • An attacker may read files accessible to the application process
  • The application may disclose resolved entity content through error responses
  • The server could make outbound requests to attacker-controlled or internal services
  • Internal network details or service metadata could be exposed
  • Availability may be affected through resource-intensive XML processing

General mitigation guidance

Mitigation generally focuses on making XML parsing safe by default and reducing trust in request content.

Common defensive patterns include:

  • Disable DTD processing and external general and parameter entities
  • Use a hardened, restrictive XML parser configuration for every untrusted XML input
  • Prefer schema-bound or non-XML formats when XML is not required
  • Validate and constrain request structure before business processing
  • Prevent outbound network access from callback workers where feasible
  • Run the application with least-privilege filesystem and network permissions
  • Avoid returning parser details or resolved content in client-visible errors

How teams detect issues like this

Organizations commonly detect this weakness through:

  • Static analysis rules identifying XML parsers created without secure-processing settings
  • Code review checks for DTD, entity, and external-schema configuration
  • Testing that submits XML containing prohibited document declarations and verifies that resolution is blocked
  • Runtime monitoring for unexpected outbound connections from callback handlers
  • Error-response review for local path, metadata, or internal service content
  • Policy enforcement requiring approved XML parsing wrappers or hardened libraries

Automated security review tools may help identify parser construction paths that do not explicitly disable external resource resolution.

Sources

SourceLink
gitee.comgitee.com/moxi159753/mogu_blog_v2/releases
github.comgithub.com/LinYuanyi1/cve-request-poc/blob/master/mogublog-poc/C10_wechat_callback_unsigned.py
github.comgithub.com/moxi624/mogu_blog_v2
github.comgithub.com/moxi624/mogu_blog_v2/blob/025d78c7ac7e19b1abf796fa3cc158d855723d15/mogu_utils/src/main/java/com/moxi/mogublog/utils/wechat/SignUtil.java
github.comgithub.com/moxi624/mogu_blog_v2/blob/025d78c7ac7e19b1abf796fa3cc158d855723d15/mogu_web/src/main/java/com/moxi/mogublog/web/restapi/WechatRestApi.java
vulncheck.comvulncheck.com/advisories/mogublog-through-6.2-xml-external-entity-injection-in-the-unauthenticated-wechat-callback-endpoint

Frequently asked

questions

Yes. The affected callback endpoint may accept attacker-controlled XML over HTTP without authentication, so exploitation can occur remotely when the endpoint is exposed.

The attacker generally needs network access to the WeChat callback endpoint. Access to the host filesystem or internal network is not required beforehand; the parser performs those operations using the application's permissions.

Use a hardened XML parser configuration that disables DTD processing and all external entity and external resource resolution, while limiting parser resource use and suppressing sensitive error details.

Standardize secure XML parsing utilities, enforce parser configuration through code review and automated analysis, test untrusted XML paths, and apply least-privilege filesystem and network controls.

Find out what's already
exploitable in your codebase.