# CVE-2022-3552: Unrestricted Upload of File with Dangerous Type in boxbilling/boxbilling

> Attackers can upload malicious files to BoxBilling, potentially leading to remote code execution on the server.

- **Severity:** High 7.2 (`CVSS:3.0/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:** 17 Oct 2022
- **Updated:** 12 May 2025
- **Also known as:** GHSA-r3mf-wrm4-mjqq

## What is CVE-2022-3552?

CVE-2022-3552 is a high-severity vulnerability in boxbilling/boxbilling, published on 17 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type in GitHub repository boxbilling/boxbilling prior to 0.0.1.

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

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

It affects 1 product.


Products: Boxbilling Boxbilling.

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

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

## Is CVE-2022-3552 being exploited?

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

Public exploit code:

- BoxBilling<=4.22.1.5 - Remote Code Execution (RCE) (github_poc): https://github.com/0xk4b1r/CVE-2022-3552
-  CVE-2022-3552 RCE with detailed exploitation steps (github_poc): https://github.com/BakalMode/CVE-2022-3552
- BoxBilling<=4.22.1.5 - Remote Code Execution (RCE) (exploitdb)

## Other vulnerabilities in boxbilling/boxbilling

- [CVE-2020-23647](https://insights.sbomify.com/CVE-2020-23647/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3552 is a high-severity vulnerability in boxbilling/boxbilling, published on 17 Oct 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-3552 exists.

Affected product: boxbilling/boxbilling. 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-3552/ (Markdown: https://insights.sbomify.com/CVE-2022-3552/index.md)
```

## Sources

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

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