# CVE-2020-28860: SQL injection in n/a

> Authenticated attackers can perform blind SQL injection in OpenAsset DAM to read sensitive database information.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Dec 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-7q5m-m6v8-m536

## What is CVE-2020-28860?

CVE-2020-28860 is a high-severity SQL injection vulnerability in n/a, published on 14 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenAssetDigital Asset Management (DAM) through 12.0.19 does not correctly sanitize user supplied input, incorporating it into its SQL queries, allowing for authenticated blind SQL injection.

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

## Which versions are affected by CVE-2020-28860?

It affects 1 product.


Products: Openasset Digital Asset Management.

## How do I fix CVE-2020-28860?

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

## Is CVE-2020-28860 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28858](https://insights.sbomify.com/CVE-2020-28858/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-28856](https://insights.sbomify.com/CVE-2020-28856/): Auth bypass in n/a (high 7.5)
- [CVE-2020-28857](https://insights.sbomify.com/CVE-2020-28857/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-28859](https://insights.sbomify.com/CVE-2020-28859/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-28861](https://insights.sbomify.com/CVE-2020-28861/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28860 and fix it if it is affected.

What it is: CVE-2020-28860 is a high-severity SQL injection vulnerability in n/a, published on 14 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28860 in the wild and no public exploit code.

Affected product: n/a. 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-2020-28860/ (Markdown: https://insights.sbomify.com/CVE-2020-28860/index.md)
```

## Sources

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

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