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

> An attacker can upload malicious files to HkCms via the getFileName method, potentially leading to remote code execution.

- **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:** 20 Nov 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-j27h-7c89-c3c6

## What is CVE-2024-52677?

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

### Official description

HkCms <= v2.3.2.240702 is vulnerable to file upload in the getFileName method in /app/common/library/Upload.php.

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

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

It affects 1 product.


Products: Hkcms Hkcms.

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

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

## Is CVE-2024-52677 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25761](https://insights.sbomify.com/CVE-2025-25761/): Path traversal in n/a (high 7.2)
- [CVE-2023-40786](https://insights.sbomify.com/CVE-2023-40786/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2025-5013](https://insights.sbomify.com/CVE-2025-5013/): HkCms Search index.html cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52677 is a critical vulnerability in n/a, published on 20 Nov 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-52677 in the wild and no public exploit code.

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-52677/ (Markdown: https://insights.sbomify.com/CVE-2024-52677/index.md)
```

## Sources

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

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