# CVE-2022-26041: Path traversal in RCCMD

> An authenticated administrator can read or modify arbitrary files on the server via a directory traversal vulnerability in RCCMD.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-87hq-43vh-pgxc

## What is CVE-2022-26041?

CVE-2022-26041 is a medium-severity path traversal vulnerability in GENEREX SYSTEMS Computervertriebsgesellschaft mbH RCCMD, published on 13 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Directory traversal vulnerability in RCCMD 4.26 and earlier allows a remote authenticated attacker with an administrative privilege to read or alter an arbitrary file on the server via unspecified vectors.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Generex Rccmd.

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

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

## Is CVE-2022-26041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26041 is a medium-severity path traversal vulnerability in GENEREX SYSTEMS Computervertriebsgesellschaft mbH RCCMD, published on 13 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26041 in the wild and no public exploit code.

Affected product: GENEREX SYSTEMS Computervertriebsgesellschaft mbH RCCMD. 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-26041/ (Markdown: https://insights.sbomify.com/CVE-2022-26041/index.md)
```

## Sources

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

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