Quick answers
- Is CVE-2025-13816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-13816 being exploited in the wild.
- How severe is CVE-2025-13816?
- Medium severity, with a CVSS score of 6.3, published 1 December 2025.
- Which products and versions are affected?
- Moxi159753 Mogu Blog v2 up to 5.2.
- Is there a fix for CVE-2025-13816?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-13816 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-13816?
- Check whether you run Mogublog Project Mogublog or Moxi159753 Mogu Blog v2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic zip slip (path traversal) flaw in the FileOperation.unzip() function accessed via the /networkDisk/unzipFile endpoint. By crafting a malicious ZIP archive with path traversal sequences (e.g., "../../../") in filenames, an attacker can write files outside the intended extraction directory. The attack requires network access and does not require authentication. An attacker can achieve arbitrary file write on the server, potentially leading to remote code execution. The vendor was notified early but did not respond or provide a patch.
Affected products
- moxi159753 Mogu Blog v2 up to 5.2
Timeline
- 2025-12-01: disclosed: Publicly disclosed on GitHub
- 2025-12-01: advisory: CVE-2025-13816 published