# CVE-2024-9278: HuankeMao SCRM Administrator Backend WxkConfig.php upload_domain_verification_file unrestricted upload

> Remote attackers with permissions can upload arbitrary files via the domain verification feature, potentially leading to code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-m794-h492-36rv

## What is CVE-2024-9278?

CVE-2024-9278 is a medium-severity vulnerability in HuankeMao SCRM, published on 27 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in HuankeMao SCRM up to 0.0.3. Affected by this issue is the function upload_domain_verification_file of the file WxkConfig.php of the component Administrator Backend. The manipulation of the argument domain_verification_file leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2024-9278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-9278 is a medium-severity vulnerability in HuankeMao SCRM, published on 27 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9278 exists.

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

## Sources

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

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