# CVE-2020-37144: Exagate Sysguard 6001 - Cross-Site Request Forgery (Add Admin)

> Attackers can trick users into submitting a malicious form to create unauthorized admin accounts on Exagate Sysguard 6001 devices.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-gm75-xf4f-5gc3

## What is CVE-2020-37144?

CVE-2020-37144 is a medium-severity vulnerability in Exagate Sysguard 6001, published on 5 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Exagate SYSGuard 6001 contains a cross-site request forgery vulnerability that allows attackers to create unauthorized admin accounts through a crafted HTML form. Attackers can trick users into submitting a malicious form to /kulyon.php that adds a new user with administrative privileges without the victim's consent.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2020-37144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37144 is a medium-severity vulnerability in Exagate Sysguard 6001, published on 5 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-37144 in the wild and no public exploit code.

Affected product: Exagate Sysguard 6001. 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-37144/ (Markdown: https://insights.sbomify.com/CVE-2020-37144/index.md)
```

## Sources

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

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