# CVE-2020-37135: AMSS++ 4.7 - Backdoor Admin Account

> Attackers can gain unauthorized administrative access to AMSS++ by logging in with hardcoded default credentials.

- **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:** 6 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-ffff-75w5-5j62

## What is CVE-2020-37135?

CVE-2020-37135 is a critical vulnerability in Amssplus AMSS++, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AMSS++ 4.7 contains an authentication bypass vulnerability that allows attackers to access administrative accounts using hardcoded credentials. Attackers can log in with the default admin username and password '1234' to gain unauthorized administrative access to the system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2020-37135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37135 is a critical vulnerability in Amssplus AMSS++, published on 6 Feb 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-37135 exists.

Affected product: Amssplus AMSS++. 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-37135/ (Markdown: https://insights.sbomify.com/CVE-2020-37135/index.md)
```

## Sources

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

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