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

> Unauthenticated attackers can upload malicious files to the web root to execute code via a web shell.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-7r5f-jp39-68j3

## What is CVE-2022-47769?

CVE-2022-47769 is a critical vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file write vulnerability in Serenissima Informatica Fast Checkin v1.0 allows unauthenticated attackers to upload malicious files in the web root of the application to gain access to the server via the web shell.

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

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

It affects 1 product.


Products: Serinf Fast Checkin.

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

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

## Is CVE-2022-47769 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-47770](https://insights.sbomify.com/CVE-2022-47770/): SQL injection in n/a (critical 9.8)
- [CVE-2022-47768](https://insights.sbomify.com/CVE-2022-47768/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47769 is a critical vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47769 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-47769/ (Markdown: https://insights.sbomify.com/CVE-2022-47769/index.md)
```

## Sources

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

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