CVE-2022-46020 File upload in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2022-46020 and fix it if it is affected.
What it is: CVE-2022-46020 is a critical vulnerability in n/a, published on 20 Dec 2022. 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-46020 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-46020/ (Markdown: https://insights.sbomify.com/CVE-2022-46020/index.md)
Attackers can achieve remote code execution by uploading malicious files due to insufficient validation of file types in WBCE CMS.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2022-46020?
CVE-2022-46020 is a critical vulnerability in n/a, published on 20 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
WBCE CMS v1.5.4 can implement getshell by modifying the upload file type.
Weakness: CWE-434
Which versions are affected by CVE-2022-46020?
It affects 1 product.
Products include Wbce Wbce Cms.
How do I fix CVE-2022-46020?
No fix has been published for CVE-2022-46020 yet. Limit exposure of the affected software until one is available.
Is CVE-2022-46020 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46020 exists.
Public exploit code: 1 Nuclei template.
Other vulnerabilities in n/a
- CVE-2023-39796 SQL injection in n/a
- CVE-2021-3817 SQL Injection in wbce/wbce_cms
- CVE-2025-65950 WBCE CMS is Vulnerable to Time-Based Blind SQL Injection through groups[] Parameter
- CVE-2025-67504 WBCE CMS has Weak Random Number Generator in Password Generation Function
- CVE-2022-50936 WBCE CMS 1.5.2 - Remote Code Execution (RCE) (Authenticated)
Sources
Also known as GHSA-6frp-xc6r-j375.