# CVE-2021-42897: Command injection in n/a

> Remote attackers can execute arbitrary commands via the r_name parameter in datarec.php, leading to full system compromise.

- **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:** 16 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j76v-x5jp-f9gj

## What is CVE-2021-42897?

CVE-2021-42897 is a critical command injection vulnerability in n/a, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote command execution (RCE) vulnerability was found in FeMiner wms V1.0 in /wms/src/system/datarec.php. The $_POST[r_name] is directly passed into the $mysqlstr and is executed by exec.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Feminer Wms Project Feminer Wms.

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

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

## Is CVE-2021-42897 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25994](https://insights.sbomify.com/CVE-2025-25994/): SQL injection in n/a (high 7.5)
- [CVE-2025-25997](https://insights.sbomify.com/CVE-2025-25997/): Path traversal in n/a (high 7.5)
- [CVE-2025-25992](https://insights.sbomify.com/CVE-2025-25992/): SQL injection in n/a (medium 5.1)
- [CVE-2025-25993](https://insights.sbomify.com/CVE-2025-25993/): SQL injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42897 is a critical command injection vulnerability in n/a, published on 16 May 2022. 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-42897 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-2021-42897/ (Markdown: https://insights.sbomify.com/CVE-2021-42897/index.md)
```

## Sources

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

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