SQL Injection in extension "sgalinski Cookie Consent" (sg_cookie_optin)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TYPO3 | Extension "sgalinski Cookie Consent" | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Typo3 | Extension Sgalinski Cookie Consent |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.366% probability within 30 days)
| Link | Providers |
|---|---|
| https://typo3.org/security/advisory/typo3-ext-sa-2026-029 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Typo3
Typo3 extension Sgalinski Cookie Consent |
|
| Vendors & Products |
Typo3
Typo3 extension Sgalinski Cookie Consent |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|