Description
The backend module for reviewing the consent history accepted sorting, grouping and index options from the request and used them in a database query without validation. Only the filter conditions of that query were bound as parameters. A backend user with access to the history or statistics functions could use this to read arbitrary data from the database, including password hashes of backend and frontend users.
Published: 2026-10-20
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Read arbitrary database data, including password hashes
Action: Apply Patch
AI Analysis

Impact

A backend module in the TYPO3 sgalinski Cookie Consent extension builds a SQL query from sorting, grouping and index parameters received in a request. Only the filter conditions of the query are parameterised, while the remaining clauses are inserted directly. An attacker can supply crafted values for these parameters to manipulate the query and extract data from the database. The vulnerability allows a backend user with access to the history or statistics functions to read arbitrary rows, including sensitive values such as password hashes of both backend and frontend users. Based on the description, it is inferred that the flaw permits arbitrary SQL injection when a backend user supplies malicious sorting, grouping, or index values.

Affected Systems

TYPO3 Extension - sgalinski Cookie Consent (sg_cookie_optin). Specific version numbers are not listed in the advisory, so any deployment of this extension is potentially vulnerable unless a non-affected release has been confirmed. The impact applies to systems that have the extension installed and whose backend users possess access to the history or statistics interfaces. The likely attack vector is an attacker who can log into a backend account with permission to access these interfaces.

Risk and Exploitability

The CVSS score of 7.1 indicates a medium severity vulnerability. The EPSS score of less than 1% suggests that widespread exploitation is unlikely at present, and the issue is not listed in the CISA KEV catalog. Nevertheless, the vulnerability requires a legitimate backend session with the appropriate permissions; therefore, compromising a backend account or exploiting social engineering on such an account would enable the attacker to weaponise the flaw. Once sufficient access is obtained, the attacker can execute the injection to gain full read exposure of database contents, which could lead to credential theft and further lateral movement. The likely attack vector is a valid backend session that has been compromised or granted the necessary access.

Generated by OpenCVE AI on October 20, 2026 at 15:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the "sgalinski Cookie Consent" extension to the latest released version that contains the input‑validation fix
  • Restrict backend user permissions so that only trusted staff have access to the consent history and statistics pages, reducing the attack surface
  • In the meantime, if an update is not yet available, manually validate or escape the sorting, grouping and index parameters before including them in SQL statements to prevent injection

Generated by OpenCVE AI on October 20, 2026 at 15:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 21 Oct 2026 17:15:00 +0000

Type Values Removed Values Added
First Time appeared Typo3
Typo3 extension Sgalinski Cookie Consent
Vendors & Products Typo3
Typo3 extension Sgalinski Cookie Consent

Tue, 20 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 20 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
Description The backend module for reviewing the consent history accepted sorting, grouping and index options from the request and used them in a database query without validation. Only the filter conditions of that query were bound as parameters. A backend user with access to the history or statistics functions could use this to read arbitrary data from the database, including password hashes of backend and frontend users.
Title SQL Injection in extension "sgalinski Cookie Consent" (sg_cookie_optin)
Weaknesses CWE-89
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Typo3 Extension Sgalinski Cookie Consent
cve-icon MITRE

Status: PUBLISHED

Assigner: TYPO3

Published:

Updated: 2026-10-24T07:24:17.633Z

Reserved: 2026-10-18T12:08:05.798Z

Link: CVE-2026-112064

cve-icon Vulnrichment

Updated: 2026-10-20T15:42:53.189Z

cve-icon NVD

Status : Deferred

Published: 2026-10-20T10:17:03.467

Modified: 2026-10-20T19:28:52.970

Link: CVE-2026-112064

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-21T16:45:40Z

Weaknesses
  • CWE-89

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