# CVE-2026-112064: SQL Injection in extension "sgalinski Cookie Consent" (sg_cookie_optin)


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-g9xv-qphg-5rv3

## What is CVE-2026-112064?

CVE-2026-112064 is a high-severity vulnerability in TYPO3 Extension "sgalinski Cookie Consent", published on 20 Oct 2026. 

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-112064?


## How do I fix CVE-2026-112064?

No fix has been published for CVE-2026-112064 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112064 being exploited?

There is no known exploitation of CVE-2026-112064 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112064 and fix it if it is affected.

What it is: CVE-2026-112064 is a high-severity vulnerability in TYPO3 Extension "sgalinski Cookie Consent", published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112064 in the wild and no public exploit code.

Affected product: TYPO3 Extension "sgalinski Cookie Consent". No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112064/ (Markdown: https://insights.sbomify.com/CVE-2026-112064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112064
- OSV: https://osv.dev/vulnerability/CVE-2026-112064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112064/
Summaries are generated and may contain mistakes; the official description above is the record.