# CVE-2021-32538: ARTWARE CMS - Unrestricted Upload of File

> Remote attackers can upload arbitrary files without authentication in ARTWARE CMS, leading to unrestricted code execution.

- **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:** 7 Jul 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w9qj-p795-8xwq

## What is CVE-2021-32538?

CVE-2021-32538 is a critical vulnerability in ARTWARE CMS, published on 7 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ARTWARE CMS parameter of image upload function does not filter the type of upload files which allows remote attackers can upload arbitrary files without logging in, and further execute code unrestrictedly.

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

## Which versions are affected by CVE-2021-32538?

It affects 1 product.


Products: Artware Cms Project Artware Cms.

## How do I fix CVE-2021-32538?

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

## Is CVE-2021-32538 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32538 and fix it if it is affected.

What it is: CVE-2021-32538 is a critical vulnerability in ARTWARE CMS, published on 7 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32538 in the wild and no public exploit code.

Affected product: ARTWARE CMS. 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-2021-32538/ (Markdown: https://insights.sbomify.com/CVE-2021-32538/index.md)
```

## Sources

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

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