# CVE-2026-66770: SQL Injection vulnerability in SAP Social Intelligence

> An authenticated attacker can inject SQL DDL commands to modify the database structure in SAP Social Intelligence.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-wm86-5vhp-x9q6

## What is CVE-2026-66770?

CVE-2026-66770 is a medium-severity SQL injection vulnerability in SAP_SE SAP Social Intelligence, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

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

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


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

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

## Is CVE-2026-66770 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66770 is a medium-severity SQL injection vulnerability in SAP_SE SAP Social Intelligence, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66770 in the wild and no public exploit code.

Affected product: SAP_SE SAP Social Intelligence. 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-66770/ (Markdown: https://insights.sbomify.com/CVE-2026-66770/index.md)
```

## Sources

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

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