# CVE-2019-25468: NetGain EM Plus 10.1.68 Remote Code Execution via script_test.jsp

> Unauthenticated attackers can execute arbitrary system commands via the script_test.jsp endpoint in NetGain EM Plus.

- **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:** 11 Mar 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-3grg-fgcc-7f3v

## What is CVE-2019-25468?

CVE-2019-25468 is a critical command injection vulnerability in NetGain EM Plus, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetGain EM Plus 10.1.68 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary system commands by submitting malicious parameters to the script_test.jsp endpoint. Attackers can send POST requests with shell commands embedded in the 'content' parameter to execute code and retrieve command output.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2019-25468?


## How do I fix CVE-2019-25468?

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

## Is CVE-2019-25468 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25468 and fix it if it is affected.

What it is: CVE-2019-25468 is a critical command injection vulnerability in NetGain EM Plus, published on 11 Mar 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-2019-25468 exists.

Affected product: NetGain EM Plus. 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-2019-25468/ (Markdown: https://insights.sbomify.com/CVE-2019-25468/index.md)
```

## Sources

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

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