# CVE-2024-53564: File upload in FreePBX

> High-privilege administrators can upload malicious files due to lack of type verification, potentially leading to code execution.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/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:** 2 Dec 2024
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-ccwq-3vpf-86cw

## What is CVE-2024-53564?

CVE-2024-53564 is a low-severity vulnerability in Sangoma Freepbx, published on 2 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was discovered in FreePBX 17.0.19.17. It does not verify the type of uploaded (valid FreePBX module) files, allowing high-privilege administrators to insert unwanted files. NOTE: the Supplier's position is that there is no risk beyond what high-privilege administrators are intentionally allowed to do.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Sangoma Freepbx.

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

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

## Is CVE-2024-53564 being exploited?

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

## Other vulnerabilities in Sangoma Freepbx

- [CVE-2025-57819](https://insights.sbomify.com/CVE-2025-57819/): Sangoma FreePBX Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2019-19006](https://insights.sbomify.com/CVE-2019-19006/): Sangoma FreePBX Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-73663](https://insights.sbomify.com/CVE-2026-73663/): FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover (critical 9.3)
- [CVE-2026-73665](https://insights.sbomify.com/CVE-2026-73665/): FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and AMI action injection (critical 9.3)
- [CVE-2026-46376](https://insights.sbomify.com/CVE-2026-46376/): FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53564 is a low-severity vulnerability in Sangoma Freepbx, published on 2 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53564 in the wild and no public exploit code.

Affected product: Sangoma Freepbx. 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-53564/ (Markdown: https://insights.sbomify.com/CVE-2024-53564/index.md)
```

## Sources

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

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