# CVE-2020-37168: Ecommerce Systempay 1.0 Production Key Brute Force

> Attackers can brute force the weak production secret key to forge payment signatures and manipulate transaction amounts in Ecommerce Systempay.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-2x94-2hh3-xhp5

## What is CVE-2020-37168?

CVE-2020-37168 is a critical vulnerability in Paiement Ecommerce Systempay, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ecommerce Systempay 1.0 contains a weak cryptographic implementation vulnerability that allows attackers to brute force the 16-character production secret key used for payment signature generation. Attackers can extract payment form data and signatures from POST requests to the payment endpoint, then use SHA1 hash comparison to iteratively test key candidates until discovering the correct production key, enabling them to forge valid payment signatures and manipulate transaction amounts.

Weakness: CWE-328 (Use of Weak Hash)

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


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

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

## Is CVE-2020-37168 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37168 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37168 is a critical vulnerability in Paiement Ecommerce Systempay, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37168 exists.

Affected product: Paiement Ecommerce Systempay. 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-37168/ (Markdown: https://insights.sbomify.com/CVE-2020-37168/index.md)
```

## Sources

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

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