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

> Attackers can upload malicious PHP files to execute arbitrary code on the Restaurant POS System web application.

- **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:** 1 Nov 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-9g68-8w7w-hfcv

## What is CVE-2022-43085?

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

### Official description

An arbitrary file upload vulnerability in add_product.php of Restaurant POS System v1.0 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-43085?

It affects 1 product.


Products: Codeastro Restaurant Pos System.

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

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

## Is CVE-2022-43085 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43086](https://insights.sbomify.com/CVE-2022-43086/): SQL injection in n/a (medium 4.9)
- [CVE-2024-1267](https://insights.sbomify.com/CVE-2024-1267/): CodeAstro Restaurant POS System create_account.php cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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