Quick answers
- Is CVE-2025-68391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-68391 being exploited in the wild.
- How severe is CVE-2025-68391?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- ARKETEAM Protectel BDF before 6.4.67; ARKETEAM Protectel PROTECTELMAJ before 6.5.19.
- Is there a fix for CVE-2025-68391?
- Yes: fixed in PROTECTELMAJ v6.5.19, BDF v6.4.67. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-68391 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2025-68391?
- Check whether you run ARKETEAM Protectel BDF or ARKETEAM Protectel PROTECTELMAJ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: PROTECTELMAJ v6.5.19, BDF v6.4.67
Technical details
The vulnerability (CVE-2025-68391) is an unrestricted file upload flaw in the PROTECTELMAJ and BDF modules allowing any user to upload arbitrary files and overwrite existing files in a temporary folder. When an authenticated user downloads an uploaded file, embedded JavaScript can be executed. Additional critical flaws in the same modules include authorization bypass (CVE-2025-68392), two SQL injection vulnerabilities (CVE-2025-68393, CVE-2025-68394), and stored XSS (CVE-2025-68395), all exploitable by low-privileged users.
Affected products
- ARKETEAM Protectel PROTECTELMAJ before 6.5.19
- ARKETEAM Protectel BDF before 6.4.67
Timeline
- 2026-10-30: disclosed