CVE-2026-89260: Improper Restriction of XML External Entity Reference in moxi624 MoguBlog
MoguBlog versions up to and including 6.2 contain an XML external entity (XXE) injection vulnerability in the WeChat callback handler. The vulnerability arises because the application uses an unhardened dom4j SAXReader without restrictions on DTD or external entities, allowing unauthenticated attackers to submit crafted XML with DOCTYPE declarations. This can lead to reading arbitrary local files or triggering outbound HTTP requests, with the results reflected in error responses.
AI Analysis
Technical Summary
CVE-2026-89260 describes an XML external entity injection vulnerability in MoguBlog through version 6.2. The WeChat callback handler at POST /wechat/wechatCheck processes the raw request body via SignUtil.xmlToMap(), which uses a dom4j SAXReader lacking protections against external entity processing. This allows unauthenticated remote attackers to submit XML containing DOCTYPE declarations with external parameter entities, enabling them to read local files or cause outbound HTTP requests. The resolved entities are reflected in error responses, potentially exposing sensitive information.
Potential Impact
The vulnerability allows unauthenticated remote attackers to read arbitrary local files on the server or cause the server to make outbound HTTP requests. This can lead to information disclosure of sensitive data. There is no indication of integrity or availability impact. The CVSS score is 7.5 (high), reflecting the confidentiality impact and ease of exploitation without authentication.
Mitigation Recommendations
No patch or official fix information is provided in the input data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, it is recommended to harden XML parsing by disabling DTD and external entity processing in the dom4j SAXReader used by the application, or to implement input validation to block malicious XML payloads.
CVE-2026-89260: Improper Restriction of XML External Entity Reference in moxi624 MoguBlog
Description
MoguBlog versions up to and including 6.2 contain an XML external entity (XXE) injection vulnerability in the WeChat callback handler. The vulnerability arises because the application uses an unhardened dom4j SAXReader without restrictions on DTD or external entities, allowing unauthenticated attackers to submit crafted XML with DOCTYPE declarations. This can lead to reading arbitrary local files or triggering outbound HTTP requests, with the results reflected in error responses.
CVSS v3.1
Score 7.5high
Affected software
moxi624
MoguBlog
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-89260 describes an XML external entity injection vulnerability in MoguBlog through version 6.2. The WeChat callback handler at POST /wechat/wechatCheck processes the raw request body via SignUtil.xmlToMap(), which uses a dom4j SAXReader lacking protections against external entity processing. This allows unauthenticated remote attackers to submit XML containing DOCTYPE declarations with external parameter entities, enabling them to read local files or cause outbound HTTP requests. The resolved entities are reflected in error responses, potentially exposing sensitive information.
Potential Impact
The vulnerability allows unauthenticated remote attackers to read arbitrary local files on the server or cause the server to make outbound HTTP requests. This can lead to information disclosure of sensitive data. There is no indication of integrity or availability impact. The CVSS score is 7.5 (high), reflecting the confidentiality impact and ease of exploitation without authentication.
Mitigation Recommendations
No patch or official fix information is provided in the input data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, it is recommended to harden XML parsing by disabling DTD and external entity processing in the dom4j SAXReader used by the application, or to implement input validation to block malicious XML payloads.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-11T10:52:56.668Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa41f3091cc7f384856d44e
Added to database: 09/11/2026, 15:33:04 UTC
Last enriched: 09/11/2026, 15:47:04 UTC
Last updated: 09/11/2026, 18:22:58 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.