# CVE-2024-28713: File upload in n/a

> An attacker can execute arbitrary code by uploading a crafted file to the theme management feature of the Mblog Blog system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-gmh5-hrww-qvc2

## What is CVE-2024-28713?

CVE-2024-28713 is a critical vulnerability in n/a, published on 28 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Mblog Blog system v.3.5.0 allows an attacker to execute arbitrary code via a crafted file to the theme management feature.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2024-28713?

It affects 1 product.


Products: Mtons Mblog.

## How do I fix CVE-2024-28713?

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

## Is CVE-2024-28713 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-9004](https://insights.sbomify.com/CVE-2025-9004/): mtons mblog password excessive authentication (medium 6.3)
- [CVE-2025-9005](https://insights.sbomify.com/CVE-2025-9005/): mtons mblog register information exposure (medium 6.3)
- [CVE-2025-8927](https://insights.sbomify.com/CVE-2025-8927/): mtons mblog Verification Code send_code excessive authentication (medium 6.3)
- [CVE-2024-13198](https://insights.sbomify.com/CVE-2024-13198/): langhsu Mblog Blog System login observable response discrepancy (medium 6.3)
- [CVE-2025-9647](https://insights.sbomify.com/CVE-2025-9647/): mtons mblog list cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28713 and fix it if it is affected.

What it is: CVE-2024-28713 is a critical vulnerability in n/a, published on 28 Mar 2024. 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-2024-28713 exists.

Affected product: n/a. 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-2024-28713/ (Markdown: https://insights.sbomify.com/CVE-2024-28713/index.md)
```

## Sources

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

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