# CVE-2022-46610: File upload in n/a

> Attackers can execute arbitrary code by uploading a malicious PHP file via the avatar upload function in 72crm.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-2wx5-x3v9-h4fr

## What is CVE-2022-46610?

CVE-2022-46610 is a high-severity vulnerability in n/a, published on 10 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

72crm v9 was discovered to contain an arbitrary file upload vulnerability via the avatar upload function. This vulnerability allows attackers to execute arbitrary code via a crafted PHP file.

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

## Which versions are affected by CVE-2022-46610?

It affects 1 product.


Products: 72crm Wukong Crm.

## How do I fix CVE-2022-46610?

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

## Is CVE-2022-46610 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37181](https://insights.sbomify.com/CVE-2022-37181/): File upload in n/a (critical 9.8)
- [CVE-2022-37178](https://insights.sbomify.com/CVE-2022-37178/): SQL injection in n/a (high 8.8)
- [CVE-2025-6106](https://insights.sbomify.com/CVE-2025-6106/): WuKongOpenSource WukongCRM AdminRoleController.java cross-site request forgery (medium 5.3)
- [CVE-2025-5879](https://insights.sbomify.com/CVE-2025-5879/): WuKongOpenSource WukongCRM File Upload AdminSysConfigController.java cross site scripting (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46610 and fix it if it is affected.

What it is: CVE-2022-46610 is a high-severity vulnerability in n/a, published on 10 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46610 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-2022-46610/ (Markdown: https://insights.sbomify.com/CVE-2022-46610/index.md)
```

## Sources

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

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