# CVE-2025-68391: Arbitrary File Upload in Protectel


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-gpmv-mc28-9pq5

## What is CVE-2025-68391?

CVE-2025-68391 is a medium-severity vulnerability in ARKETEAM BDF, published on 30 Oct 2026. 

### Official description

ARKETEAM Protectel modules PROTECTELMAJ and BDF are vulnerable to arbitrary file upload. Any user is able to upload arbitrary file and override existing files in a temporary folder. This vulnerability might lead to execution of embedded JavaScript scripts when an authenticated user tries to download the uploaded file. 
This issue has been fixed in: PROTECTELMAJ v6.5.19 and BDF v6.4.67

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

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


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

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

## Is CVE-2025-68391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68391 is a medium-severity vulnerability in ARKETEAM BDF, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-68391 in the wild and no public exploit code.

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

## Sources

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

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