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

> Attackers can upload arbitrary files to Docebo Community Edition, potentially leading to code execution, but the software is no longer supported.

- **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:** 22 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jc44-gwj5-3hqm

## What is CVE-2022-31362?

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

### Official description

Docebo Community Edition v4.0.5 and below was discovered to contain an arbitrary file upload vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

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

It affects 1 product.


Products: Docebo Docebo.

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

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

## Is CVE-2022-31362 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31361](https://insights.sbomify.com/CVE-2022-31361/): SQL injection in n/a (critical 9.8)
- [CVE-2009-4742](https://insights.sbomify.com/CVE-2009-4742/): SQL injection in n/a (high 7.5)
- [CVE-2008-7153](https://insights.sbomify.com/CVE-2008-7153/): SQL injection in n/a (high 7.5)
- [CVE-2006-6963](https://insights.sbomify.com/CVE-2006-6963/): Code injection in n/a (high 7.5)
- [CVE-2006-6957](https://insights.sbomify.com/CVE-2006-6957/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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