SQL Injection in friendsoftypo3/tt-address (CVE-2026-8827)
Summary
SQL injection in friendsoftypo3/tt-address (CVE-2026-8827). Risk of unauthorized operations or information disclosure. Exploitable via tt_address. Mitigation: upgrade to 8.1.2 or later.
Original description
The description as published by the source.
The AddressRepository::getSqlQuery() method constructs a database query without properly sanitizing user input, leading to SQL Injection. The method is not invoked anywhere within the extension itself and therefore poses no direct risk in a default installation. However, custom extensions that call this method with untrusted input would expose the site to SQL injection.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-8827 has been found in friendsoftypo3/tt-address.
Attackers can target a specific entry point like tt_address over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade friendsoftypo3/tt-address to 8.1.2 or later.
If unsure, ask your IT team or search "friendsoftypo3/tt-address CVE-2026-8827" on the vendor's site.
CVE-2026-8827 (friendsoftypo3/tt-address) — CWE-89
Attack surface: tt_address
Patched: 8.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in friendsoftypo3/tt-address. Attackers reach the vulnerable code path via tt_address.
Check the vendor advisory for the affected versions of friendsoftypo3/tt-address. Attack surface: tt_address.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.1.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'friendsoftypo3/tt-address' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'friendsoftypo3/tt-address' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
friendsoftypo3/tt-addressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade friendsoftypo3/tt-address to 8.1.2ステージング環境で 8.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web packagist.org