# CVE-2024-0648: Yunyou CMS Common.php unrestricted upload

> Attackers can upload malicious files via the templateFile parameter in Yunyou CMS, potentially leading to remote code execution.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-7xch-q4h4-rv7g

## What is CVE-2024-0648?

CVE-2024-0648 is a high-severity vulnerability in Yunyou CMS, published on 17 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in Yunyou CMS up to 2.2.6 and classified as critical. This vulnerability affects unknown code of the file /app/index/controller/Common.php. The manipulation of the argument templateFile leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-251374 is the identifier assigned to this vulnerability.

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

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

It affects 1 product.


Products: Yunyou Cms Project Yunyou Cms.

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

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

## Is CVE-2024-0648 being exploited?

There is no known exploitation of CVE-2024-0648 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0648 is a high-severity vulnerability in Yunyou CMS, published on 17 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0648 in the wild and no public exploit code.

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

## Sources

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

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