# CVE-2024-56908: File upload in n/a

> An authenticated attacker can upload arbitrary files via the upload_sales_file endpoint, potentially leading to remote code execution.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-qvrx-p9gg-46f8

## What is CVE-2024-56908?

CVE-2024-56908 is a medium-severity vulnerability in n/a, published on 13 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In Perfex Crm < 3.2.1, an authenticated attacker can send a crafted HTTP POST request to the affected upload_sales_file endpoint. By providing malicious input in the rel_id parameter, combined with improper input validation, the attacker can bypass restrictions and upload arbitrary files to directories of their choice, potentially leading to remote code execution or server compromise.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-1287 (Improper Validation of Specified Type of Input)

## Which versions are affected by CVE-2024-56908?


## How do I fix CVE-2024-56908?

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

## Is CVE-2024-56908 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56908 and fix it if it is affected.

What it is: CVE-2024-56908 is a medium-severity vulnerability in n/a, published on 13 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56908 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-2024-56908/ (Markdown: https://insights.sbomify.com/CVE-2024-56908/index.md)
```

## Sources

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

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