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

> Attackers can execute arbitrary code by uploading a crafted PHP file to the rconfig web application.

- **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:** 17 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-vwc9-qw9m-64xj

## What is CVE-2022-44384?

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

### Official description

An arbitrary file upload vulnerability in rconfig v3.9.6 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-44384?

It affects 1 product.


Products: Rconfig Rconfig.

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

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

## Is CVE-2022-44384 being exploited?

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

Public exploit code:

- rConfig Vendors Auth File Upload RCE (metasploit)

## Other vulnerabilities in n/a

- [CVE-2020-10221](https://insights.sbomify.com/CVE-2020-10221/): rConfig OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2020-15715](https://insights.sbomify.com/CVE-2020-15715/): Command injection in n/a (critical 9.9)
- [CVE-2020-23151](https://insights.sbomify.com/CVE-2020-23151/): Command injection in n/a (critical 9.8)
- [CVE-2020-13638](https://insights.sbomify.com/CVE-2020-13638/): Auth bypass in n/a (critical 9.8)
- [CVE-2020-10546](https://insights.sbomify.com/CVE-2020-10546/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44384 is a high-severity vulnerability in n/a, published on 17 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-44384 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-2022-44384/ (Markdown: https://insights.sbomify.com/CVE-2022-44384/index.md)
```

## Sources

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

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