CVE-2025-13813: moxi159753 Mogu Blog v2 · Missing Authorization
Affects moxi159753 Mogu Blog v2Source CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| moxi159753 Mogu Blog v2 | Affected
| Fixed in– |
AI-suggested
Given the lack of official patches, European organizations should implement compensating controls including: 1) Restrict network access to the /storage/ endpoint using firewalls or web application firewalls (WAFs) to limit exposure to trusted IPs only. 2) Monitor logs for unusual access patterns or unauthorized attempts targeting the storage management component. 3) Employ strict access control policies and ensure that default or weak credentials are not used. 4) Consider isolating Mogu Blog instances in segmented network zones to reduce lateral movement risk. 5) Regularly back up blog data to enable recovery in case of tampering or deletion. 6) Engage in threat hunting for indicators of compromise related to this vulnerability. 7) Stay alert for vendor updates or community patches and plan timely application once available. 8) If feasible, evaluate alternative blogging platforms with active security support to reduce long-term risk.
Description
A vulnerability was identified in moxi159753 Mogu Blog v2 up to 5.2. This issue affects some unknown processing of the file /storage/ of the component Storage Management Endpoint. The manipulation leads to missing authorization. The attack can be initiated remotely. The attack's complexity is rated as high. The exploitability is assessed as difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
References
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- github.com/Xzzz111/exps/blob/main/archives/mogu_blog_v2-broken_access_control-1/report.md (opens in a new tab)
- github.com/Xzzz111/exps/blob/main/archives/mogu_blog_v2-broken_access_control-1/report.md (opens in a new tab)