# CVE-2025-13813: moxi159753 Mogu Blog v2 Storage Management Endpoint storage authorization

> Attackers can access the storage management endpoint without proper authorization, potentially reading or modifying stored files.

- **Severity:** Medium 6.3 (`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:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-f45p-2w4f-m93w

## What is CVE-2025-13813?

CVE-2025-13813 is a medium-severity missing authorization vulnerability in moxi159753 Mogu Blog v2, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-13813?

It affects 1 product.


Products: Mogublog Project Mogublog.

## How do I fix CVE-2025-13813?

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

## Is CVE-2025-13813 being exploited?

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

## Other vulnerabilities in moxi159753 Mogu Blog v2

- [CVE-2025-13814](https://insights.sbomify.com/CVE-2025-13814/): moxi159753 Mogu Blog v2 uploadPicsByUrl LocalFileServiceImpl.uploadPictureByUrl server-side request forgery (medium 6.9)
- [CVE-2022-30517](https://insights.sbomify.com/CVE-2022-30517/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-13815](https://insights.sbomify.com/CVE-2025-13815/): moxi159753 Mogu Blog v2 pictures unrestricted upload (medium 5.3)
- [CVE-2025-13816](https://insights.sbomify.com/CVE-2025-13816/): moxi159753 Mogu Blog v2 ZIP File unzipFile FileOperation.unzip path traversal (medium 5.3)
- [CVE-2023-2101](https://insights.sbomify.com/CVE-2023-2101/): moxi624 Mogu Blog v2 uploadPicsByUrl uploadPictureByUrl absolute path traversal (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13813 and fix it if it is affected.

What it is: CVE-2025-13813 is a medium-severity missing authorization vulnerability in moxi159753 Mogu Blog v2, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13813 exists.

Affected product: moxi159753 Mogu Blog v2. 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-2025-13813/ (Markdown: https://insights.sbomify.com/CVE-2025-13813/index.md)
```

## Sources

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

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