Skip to main content
VulnerabilityPublished Updated

CVE-2026-112064: TYPO3 Extension "sgalinski Cookie Consent" · SQL Injection

Affects TYPO3 Extension "sgalinski Cookie Consent"Source CVE Database V5

0

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

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Extension "sgalinski Cookie Consent"sgalinski/sg-cookie-optinAffected
  • >=8.0.0 <8.1.12
Fixed in
  • 8.1.12
Extension "sgalinski Cookie Consent"sgalinski/sg-cookie-optinAffected
  • <7.4.6
Fixed in
  • 7.4.6
Packagistsgalinski/sg-cookie-optinpkg:composer/sgalinski/sg-cookie-optinOther threatsAffected
  • >=8.0.0 <8.1.12
  • <7.4.6
Fixed in
  • 8.1.12
  • 7.4.6

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.

References

Community reviews

Loading reviews…