Live Active security incident? Get immediate response
CVE Record

CVE-2026-12206: Grit42 Grit data_table_entity.rb DataTableEntity sql injection

A vulnerability was identified in Grit42 Grit up to 0.11.0. This issue affects the function Grit::Assays::DataTableEntity of the file modules/assays/backend/app/models/grit/assays/data_table_entity.rb. The manipulation leads to sql injection. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

MediumCVSS 6.5Not KEV-listed Updated
Glexia's Take moderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-12206 is a SQL injection issue in Grit42 Grit through 0.11.0. A remote authenticated user may be able to interfere with database queries, affecting confidentiality, integrity, and availability. Public exploit material is referenced, but the provided sources do not show confirmed active exploitation.

Executive priority

Treat this as a near-term vulnerability management item. Public exploit availability increases urgency, but authentication requirements and lack of confirmed active exploitation keep it below emergency level. Prioritize exposed or multi-user deployments first.

Technical view

The issue affects Grit::Assays::DataTableEntity in modules/assays/backend/app/models/grit/assays/data_table_entity.rb. VulDB maps it to CWE-89 and CWE-74 with CVSS v2 6.5: AV:N/AC:L/Au:S/C:P/I:P/A:P. The vendor reportedly did not respond, and no fixed version is named in the supplied sources.

Likely exposure

Exposure is likely limited to organizations running Grit42 Grit versions 0.1 through 0.11.0, especially where the affected functionality is reachable by authenticated users over a network. The submission reference specifically discusses 0.8.0 through 0.11.0, so confirm exact deployed versions.

Exploitation context

The vulnerability is remotely reachable and appears to require permissions or authentication. Public exploit material is referenced by VulDB and GitHub. However, KEV is false and the supplied sources do not state that attacks are occurring in the wild.

Researcher notes

Evidence is mostly from VulDB and the referenced public research repository. The record says the vendor was contacted but did not respond. No official remediation, patch version, or in-the-wild exploitation evidence is included in the supplied sources.

Mitigation direction

  • Identify all Grit42 Grit deployments and versions.
  • Restrict access to Grit to trusted users and networks.
  • Review vendor channels for an official advisory or fixed release.
  • Reduce database privileges used by the Grit application where feasible.
  • Monitor application and database logs for abnormal query errors or access patterns.

Validation and detection

  • Confirm whether Grit versions 0.1 through 0.11.0 are deployed.
  • Verify whether the affected DataTableEntity code path exists.
  • Determine whether the affected functionality is reachable remotely.
  • Confirm authentication and role requirements for access.
  • Review logs for suspicious database errors without testing destructive payloads.
Prepared
Confidence
medium
Sources
7

Based on public source material and reviewed before publication.

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 · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
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

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-12206 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 profile CVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

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.

4 CVSS vectors
6 Timeline events
0 ADP providers
6 Source links

CVSS vector scores

4 official scores

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.

Score Version Severity Vector Exploit Impact Source
6.5 CVSS 2.0 Medium AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 8 6.4 VulDB
6.3 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
6.3 CVSS 3.0 Medium CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
5.3 CVSS 4.0 Medium CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P VulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.3 Medium
CVSS 4.0 vector shape for CVE-2026-12206 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

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

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

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

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
Grit42 Grit 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11.0 Listed
Weakness

CWE details

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

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

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