# CVE-2021-25857: Code injection in n/a

> Authenticated attackers can execute arbitrary code via the font_type parameter in superMicro-CMS setup.php.

- **Severity:** High 7.2 (`CVSS:3.1/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:** 11 Aug 2023
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-8qw7-5hmf-cjwv

## What is CVE-2021-25857?

CVE-2021-25857 is a high-severity code injection vulnerability in n/a, published on 11 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in pcmt superMicro-CMS version 3.11, allows authenticated attackers to execute arbitrary code via the font_type parameter to setup.php.

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

It affects 1 product.


Products: Supermicro-Cms Project Supermicro-Cms.

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

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

## Is CVE-2021-25857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25856](https://insights.sbomify.com/CVE-2021-25856/): Path traversal in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-25857 is a high-severity code injection vulnerability in n/a, published on 11 Aug 2023. 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-2021-25857 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-2021-25857/ (Markdown: https://insights.sbomify.com/CVE-2021-25857/index.md)
```

## Sources

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

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