# CVE-2020-37123: Pinger 1.0 - Remote Code Execution

> Attackers can execute arbitrary system commands and write PHP files via unsanitized input in the ping and socket parameters of Pinger.

- **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:** 5 Feb 2026
- **Updated:** 6 Feb 2026
- **Also known as:** GHSA-mxm5-68jf-rh35

## What is CVE-2020-37123?

CVE-2020-37123 is a critical command injection vulnerability in wcchandler Pinger, published on 5 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pinger 1.0 contains a remote code execution vulnerability that allows attackers to inject shell commands through the ping and socket parameters. Attackers can exploit the unsanitized input in ping.php to write arbitrary PHP files and execute system commands by appending shell metacharacters.

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

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


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

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

## Is CVE-2020-37123 being exploited?

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

Public exploit code:

- Pinger 1.0 - Remote Code Execution (nuclei): http/cves/2020/CVE-2020-37123.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37123 is a critical command injection vulnerability in wcchandler Pinger, published on 5 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-37123 exists.

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

## Sources

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

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