CVE-2026-112064: TYPO3 Extension "sgalinski Cookie Consent" · SQL Injection
Affects TYPO3 Extension "sgalinski Cookie Consent"Source CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 8.1.12 or 7.4.6 soon.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.1.12, 7.4.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Extension "sgalinski Cookie Consent" and sgalinski/sg-cookie-optin to 8.1.12 or 7.4.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Extension "sgalinski Cookie Consent"sgalinski/sg-cookie-optin | Affected
| Fixed in
|
| Extension "sgalinski Cookie Consent"sgalinski/sg-cookie-optin | Affected
| Fixed in
|
Packagistsgalinski/sg-cookie-optinpkg:composer/sgalinski/sg-cookie-optinOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict backend user access to the consent history and statistics functions to trusted personnel only.
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.