Skip to main content

ARKETEAM Protectel EUVDEUVD-2025-211225

| CVE-2025-68393 HIGH
SQL Injection (CWE-89)
2026-10-30 CERT-PL GHSA-fxxw-wh9q-438c
8.4
CVSS 4.0 · Vendor: CERT-PL
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged account on adjacent network
  2. Exploit
    Submit crafted "Utilisateur" parameter
  3. Execution
    Trigger SQL injection in query
  4. Impact
    Read/modify arbitrary database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated low-privileged user account on the affected ARKETEAM Protectel module (PROTECTELMAJ before v6.5.19 or BDF before v6.4.67) and, per the CVSS vector, adjacent-network reachability (AV:A) rather than arbitrary internet access. The concrete trigger is unsanitized input supplied through the "Utilisateur" parameter. Limiting factors: it is not remote-unauthenticated (an account is needed), the attacker must reach the application over the adjacent/local network segment, and only these two niche modules in the stated version ranges are affected. Note the input CVSS encodes PR:H while the description says the required account is low-privileged; the privilege bar should be confirmed with the vendor.

Impact

This is a CWE-89 SQL injection in the ARKETEAM Protectel modules PROTECTELMAJ and BDF, reachable through the "Utilisateur" parameter. The CNA-supplied CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L, base 8.4) describes an adjacent-network, low-complexity attack with high confidentiality and integrity impact. A clear signal conflict exists: the CVSS vector encodes PR:H (high privileges required), yet the description explicitly states the flaw is triggered by input from a "low privileged user" - these disagree, and the description's lower bar is the more exploit-relevant of the two; verify the true privilege requirement with the vendor/CERT-PL advisory. On the decision side, the input carries a vuln.today priority of "this_week" and a vendor patch is available, but there is no EPSS probability, no CISA KEV listing, and no public exploit or PoC reference supplied. So while the technical impact is high (full read/write of the backing database typical of SQLi), the real-world urgency signals are moderate rather than critical: no evidence of active exploitation and no published exploit code, against a niche vendor product. Net: a genuine high-impact, patch-now-this-week issue for anyone running these modules, but not an emergency mass-exploitation scenario based on the available signals.

Exploit ScenarioDerived

An attacker with a low-privileged account on the Protectel application, positioned on the adjacent network, submits crafted input in the "Utilisateur" parameter that is not properly neutralized before being used in a SQL query. This lets them read or modify arbitrary database contents (credentials, business records) belonging to other users. No public exploit code or PoC was identified in the provided sources.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 30, 2026

SQL injection in the ARKETEAM Protectel modules PROTECTELMAJ (before 6.5.19) and BDF (before 6.4.67) allows an authenticated user with adjacent-network access to inject arbitrary SQL through the "Utilisateur" parameter, potentially reading and modifying database contents and affecting availability. The issue is CWE-89 and has vendor-released fixes; no public exploit code or confirmed active exploitation was identified at time of analysis. Exposure is limited by the need for a valid account and adjacent-network reachability, and the supplied privilege metric is inconsistent with the described low-privileged user requirement.

RemediationAI

Upgrade PROTECTELMAJ to v6.5.19 or later and BDF to v6.4.67 or later; these are the fixed versions identified by the vendor and EUVD. No separate workaround is described in the available sources. Because the assessed prerequisites are an authenticated account and adjacent-network reachability, exposure is lower where the modules are not reachable from untrusted adjacent segments and where low-privileged accounts are restricted, but those measures do not correct the SQL injection. Vendor advisory: https://protectel.arketeam.com/; CERT-PL: https://cert.pl/en/posts/2026/10/CVE-2025-68391.

Affected VersionsENISA

BDF 0 <6.4.67
PROTECTELMAJ 0 <6.5.19

Affected Packages

euvd bdf fix: 6.4.67
euvd protectelmaj fix: 6.5.19

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a CWE-89 SQL injection: input supplied through the "Utilisateur" parameter is not properly neutralized before being incorporated into a SQL query, allowing a user who can reach that parameter to alter query logic. The affected code is in the ARKETEAM Protectel modules PROTECTELMAJ and BDF, identified by CPEs cpe:2.3:a:arketeam:protectelmaj and cpe:2.3:a:arketeam:bdf. Per the independent assessment, exploitation requires an authenticated account and adjacent-network reachability (AV:A); the supplied CVSS 4.0 vector records PR:H while the description and the CVSS 3.1 assessment describe a low-privileged user, so the exact privilege requirement is not fully consistent across sources and should be confirmed with the vendor. The trigger is the "Utilisateur" parameter; how the application constructs or invokes the underlying query beyond that is not described in the available sources.

Know when Protectelmaj gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CERT-PL) PRIMARY 8.4 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
vuln.today AI 7.6 HIGH

Description states a low-privileged user triggers it, so PR:L not PR:H; AV:A and AC:L kept per CNA; SQLi yields C:H/I:H with limited availability impact.

3.1 AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (CERT-PL).

CVSS VectorVendor: CERT-PL

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 30, 2026 - 12:01 EUVD
CVE Published
Oct 30, 2026 - 11:37 cve.org
HIGH 8.4

DescriptionCVE.org

ARKETEAM Protectel modules PROTECTELMAJ and BDF are vulnerable to SQL injection vulnerability. Improper neutralization of input provided by a low privileged user into "Utilisateur" parameter allows for SQL Injection attacks. This issue has been fixed in: PROTECTELMAJ v6.5.19 and BDF v6.4.67

Executive ViewAI

Why It Matters

ARKETEAM Protectel modules PROTECTELMAJ and BDF contain a high-severity SQL injection vulnerability that requires an authenticated user with adjacent-network access. This could allow unauthorized database reads, modifications, and availability disruptions, impacting data integrity and operational continuity.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Rare
obscure French vendor module, negligible broad enterprise footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy