# CVE-2026-105781: Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerab


- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-r3v6-wxx2-553x

## What is CVE-2026-105781?

CVE-2026-105781 is a critical vulnerability in Adobe Campaign Classic, published on 27 Oct 2026. 

### Official description

Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary SQL commands, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue does not require user interaction. Scope is changed.

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

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


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

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

## Is CVE-2026-105781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105781 is a critical vulnerability in Adobe Campaign Classic, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105781 in the wild and no public exploit code.

Affected product: Adobe Campaign Classic. 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-105781/ (Markdown: https://insights.sbomify.com/CVE-2026-105781/index.md)
```

## Sources

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

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