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

> Remote code execution is possible in Billing System Project via the createProduct.php component, allowing attackers to execute arbitrary commands.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-2vh8-37v3-crfv

## What is CVE-2022-41437?

CVE-2022-41437 is a high-severity vulnerability in n/a, published on 30 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Billing System Project v1.0 was discovered to contain a remote code execution (RCE) vulnerability via the component /php_action/createProduct.php.

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

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

It affects 1 product.


Products: Billing System Project Project Billing System Project.

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

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

## Is CVE-2022-41437 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43213](https://insights.sbomify.com/CVE-2022-43213/): SQL injection in n/a (critical 9.8)
- [CVE-2022-41439](https://insights.sbomify.com/CVE-2022-41439/): SQL injection in n/a (high 7.2)
- [CVE-2022-41440](https://insights.sbomify.com/CVE-2022-41440/): SQL injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41437 is a high-severity vulnerability in n/a, published on 30 Sep 2022. 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-2022-41437 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-41437/ (Markdown: https://insights.sbomify.com/CVE-2022-41437/index.md)
```

## Sources

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

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