/

CVE-2026-50769

Severity:

CRITICAL RISK

(9.8)

SQL Injection (CWE-89) in Brainformatik CRM+ Endpoint

CVE-2026-50769

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Database Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical, time-based SQL injection vulnerability in the Brainformatik CRM+ appointment conflict-checking endpoint may allow an attacker to manipulate database queries through crafted request input. Depending on database permissions and application exposure, successful exploitation could compromise sensitive data, alter records, or affect application availability.

Affected context

The vulnerability occurs in CRM+ deployments up to and including version 2025.6 when the appointment conflict-checking functionality is accessible through the CheckConflictOfDates endpoint. Risk is increased when request parameters are incorporated into database queries without adequate parameterization, and when the endpoint is exposed to untrusted users or the public internet.

Exploit preconditions

  • Attack surface: The HTTP appointment conflict-checking endpoint at index.php?module=Appointments&action=CheckConflictOfDates&ajaxSkipHeader=true
  • Required access: Ability to send requests accepted by the endpoint; authentication requirements depend on deployment configuration
  • Trigger point: Processing of appointment date or conflict-checking request parameters
  • Why exploitation is possible: Input may reach database query construction without sufficient separation between data and SQL syntax, allowing response timing to reveal query behavior

Why this happens

The underlying bug is SQL injection, mapped to CWE-89. The application appears to process externally controlled request data in a database query without consistently using parameterized statements, safe query builders, or equivalent separation mechanisms. Time-based behavior can make the issue observable even when query results are not returned directly, because database response delays may disclose whether injected conditions were evaluated.

Potential impact

  • An attacker may read sensitive database records
  • An attacker could modify or delete application data
  • Database credentials or other stored secrets may be exposed
  • The application may experience degraded availability or denial of service
  • Downstream CRM users, customers, or integrations may be affected

General mitigation guidance

Mitigation generally focuses on removing SQL syntax from the influence of request data and reducing the trust placed in endpoint inputs.

Common defensive patterns include:

  • Use parameterized queries, prepared statements, or vetted query-builder abstractions for all database operations
  • Apply strict allowlisted validation for date, identifier, and calendar-related fields
  • Avoid dynamically concatenating request values into SQL statements
  • Use database accounts with only the permissions required by the appointment functionality
  • Restrict endpoint exposure and require appropriate authentication and authorization
  • Return generic errors and avoid exposing database details or timing-sensitive diagnostics
  • Add regression tests covering malformed, unexpected, and boundary-value inputs

How teams detect issues like this

Organizations can identify related SQL injection risks through:

  • Static analysis rules for string concatenation or interpolation inside SQL construction
  • Code review checks for request parameters passed directly to database APIs
  • Dynamic testing that monitors database errors, anomalous response timing, and unexpected query behavior
  • Web application firewall or API gateway policies that detect suspicious query-oriented input patterns
  • Database audit logs showing unusual query volume, access patterns, or operations from the CRM application account
  • Automated security testing in CI pipelines and neutral code-review tools that flag missing parameterization

Sources

SourceLink
github.comgithub.com/Henkel-CyberVM/CVEs/tree/main/CVE-2026-50769
brainformatik.combrainformatik.com/

Frequently asked

questions

It may be remotely exploitable when the appointment conflict-checking endpoint is reachable by an attacker and accepts requests without sufficient access controls.

Not necessarily. The requirement depends on the CRM+ deployment, endpoint authorization, and whether an attacker can obtain valid credentials or reach the application through another trusted interface.

Use parameterized database queries or equivalent safe query abstractions, validate inputs with strict allowlists, and ensure the database account has minimal privileges.

Combine secure database APIs with code review, static analysis, dynamic security testing, endpoint authorization, database auditing, and regression tests for all externally controlled query inputs.

Find out what's already
exploitable in your codebase.