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

> Remote attackers can exploit a time-based SQL injection in the login page to extract data or execute code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fhgh-fg4r-6pjp

## What is CVE-2020-26944?

CVE-2020-26944 is a critical SQL injection vulnerability in n/a, published on 16 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Aptean Product Configurator 4.61.0000 on Windows. A Time based SQL injection affects the nameTxt parameter on the main login page (aka cse?cmd=LOGIN). This can be exploited directly, and remotely.

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

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

It affects 1 product.


Products: Aptean Product Configurator.

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

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

## Is CVE-2020-26944 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-26944 is a critical SQL injection vulnerability in n/a, published on 16 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26944 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-26944/ (Markdown: https://insights.sbomify.com/CVE-2020-26944/index.md)
```

## Sources

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

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