# CVE-2025-5993: Path Traversal in ITCube CRM

> Unauthenticated attackers can exploit a path traversal vulnerability to download arbitrary files accessible by the web server process.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-rvcg-9g68-cr9c

## What is CVE-2025-5993?

CVE-2025-5993 is a critical path traversal vulnerability in ITCube CRM, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ITCube CRM in versions from 2023.2 through 2025.2 is vulnerable to path traversal. Unauthenticated remote attacker is able to exploit vulnerable parameter fileName and construct payloads that allow to download any file accessible by the the web server process.

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

## Which versions are affected by CVE-2025-5993?


## How do I fix CVE-2025-5993?

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

## Is CVE-2025-5993 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5993 and fix it if it is affected.

What it is: CVE-2025-5993 is a critical path traversal vulnerability in ITCube CRM, published on 8 Sep 2025. 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-2025-5993 in the wild and no public exploit code.

Affected product: ITCube CRM. 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-2025-5993/ (Markdown: https://insights.sbomify.com/CVE-2025-5993/index.md)
```

## Sources

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

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