LiveActive security incident?Get immediate response
CVE Record

CVE-2026-50769: The CRM+ application before and including version 2025.6 from Brainformatik is vulnerable to SQL Injection...

The CRM+ application before and including version 2025.6 from Brainformatik is vulnerable to SQL Injection (time-based) vulnerability. The check conflict endpoint index.php?module=Appointments&action=CheckConflictOfDates&ajaxSkipHeader=true which is used to check any conflicts for user calendar is vulnerable to SQL injection allowing an attacker to execute arbitrary code.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Brainformatik CRM+ through version 2025.6 reportedly contains a critical SQL injection flaw in a calendar conflict-checking endpoint. The supplied CVSS assessment indicates a remote, unauthenticated attacker could compromise sensitive data, alter records, or disrupt service. The description also claims arbitrary code execution, but the supplied sources do not establish the exact execution path.

Executive priority

Treat this as an immediate remediation priority for externally reachable CRM+ systems through version 2025.6. Restrict access now, confirm vendor guidance, and establish whether sensitive CRM data may have been exposed. There is no supplied evidence of active exploitation, but the reported unauthenticated attack surface and potential full impact justify urgent action.

Technical view

CVE-2026-50769 is a reported time-based SQL injection weakness, CWE-89, in index.php's Appointments CheckConflictOfDates action. Its CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction. The bundle identifies CRM+ versions through 2025.6, although its structured affected-product metadata is incomplete.

Likely exposure

Prioritize CRM+ deployments at version 2025.6 or earlier where the affected web endpoint is reachable from untrusted networks. The supplied record indicates no authentication requirement. Exposure for later releases is unclear because the bundle names no fixed version and provides incomplete affected-product metadata.

Exploitation context

The supplied bundle does not show CISA KEV inclusion or cite evidence of active exploitation. A public researcher repository is referenced, indicating public disclosure, but that alone does not prove attacks in the wild. Treat reachable affected systems as urgent because the reported attack complexity is low and potential impact is severe.

Researcher notes

The record reports time-based SQL injection and separately claims arbitrary code execution, but the bundle does not explain how database injection becomes code execution. It also lacks populated vendor, product, CPE, fixed-version, and vendor-advisory details. Validate these points before making definitive asset-matching or compromise claims.

Mitigation direction

  • Inventory Brainformatik CRM+ instances and identify versions at or below 2025.6.
  • Restrict untrusted network access to the affected endpoint while remediation is evaluated.
  • Check Brainformatik guidance for a confirmed fixed release or supported mitigation.
  • Apply the vendor-approved update or mitigation after testing and back up critical CRM data.
  • Monitor application, database, and access logs for suspicious requests or abnormal query delays.

Validation and detection

  • Confirm each CRM+ deployment's exact version and network exposure.
  • Verify whether unauthenticated users can reach the Appointments conflict-check endpoint.
  • Review web and database logs for anomalous requests, errors, or repeated response delays.
  • Use authorized, non-destructive testing to confirm remediation without exposing production data.
  • Document systems where version or remediation status cannot be established.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-50769 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-50769Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command

Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.