# CVE-2020-37002: Ajenti 2.1.36 Authenticated Remote Code Execution

> Authenticated attackers can execute arbitrary commands via the terminal API endpoint, leading to remote code execution on the Ajenti server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 29 Jan 2026
- **Updated:** 25 May 2026
- **Also known as:** GHSA-g2h7-7vxw-6v9j

## What is CVE-2020-37002?

CVE-2020-37002 is a high-severity command injection vulnerability in Ajenti, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ajenti 2.1.36 contains a post-authenticated remote command execution vulnerability that allows remote attackers to execute arbitrary commands after successful login. Attackers can leverage the /api/terminal/create endpoint to send a netcat reverse shell payload targeting a specified IP and port.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2020-37002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37002 is a high-severity command injection vulnerability in Ajenti, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37002 exists.

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

## Sources

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

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