SQL Injection in SAP Social intelligence (CVE-2026-66770)
Summary
SQL injection in SAP Social intelligence (CVE-2026-66770). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Due to an SQL Injection vulnerability in SAP Social intelligence, an authenticated attacker could directly inject an SQL DDL (Data Definition Language) string into the underlying database without further authorization. Successful exploitation could allow the attacker to make malicious changes to the database structure, resulting in a low impact to the confidentiality, integrity, and availability of the system.
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-66770 has been found in SAP Social intelligence.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SAP Social intelligence CVE-2026-66770" on the vendor's site.
CVE-2026-66770 (SAP Social intelligence) — CWE-89 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
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 SAP Social intelligence.
Check the vendor advisory for the affected versions of SAP Social intelligence.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SAP Social intelligence を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cna@sap.com
- web cna@sap.com
- web nvd.nist.gov
- web github.com