Quick answers
- Is CVE-2025-68393 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-68393 being exploited in the wild.
- How severe is CVE-2025-68393?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- ARKETEAM Protectel BDF All before 6.4.67; ARKETEAM Protectel PROTECTELMAJ All before 6.5.19.
- Is there a fix for CVE-2025-68393?
- Yes: fixed in PROTECTELMAJ v6.5.19 and BDF v6.4.67. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-68393 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-68393?
- 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 and BDF v6.4.67
Technical details
This SQL injection vulnerability in the Utilisateur parameter arises from improper neutralization of user input before incorporation into SQL queries. The flaw is exploitable by low-privileged authenticated users via direct requests, allowing them to execute arbitrary SQL commands and potentially extract, modify, or delete database records. A fix is available in PROTECTELMAJ v6.5.19 and BDF v6.4.67.
Affected products
- ARKETEAM Protectel PROTECTELMAJ All before 6.5.19
- ARKETEAM Protectel BDF All before 6.4.67
Timeline
- 2026-10-30: disclosed