# CVE-2025-55372: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted file to the Beakon Application.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-wwvf-g3f4-8mhx

## What is CVE-2025-55372?

CVE-2025-55372 is a medium-severity vulnerability in n/a, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file upload vulnerability in Beakon Application before v5.4.3 allows attackers to execute arbitrary code via uploading a crafted file.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Beakon Beakon.

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

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

## Is CVE-2025-55372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-55373](https://insights.sbomify.com/CVE-2025-55373/): Privilege escalation in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55372 is a medium-severity vulnerability in n/a, published on 2 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-55372 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-2025-55372/ (Markdown: https://insights.sbomify.com/CVE-2025-55372/index.md)
```

## Sources

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

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