# CVE-2019-25671: VA MAX 8.3.4 Remote Code Execution via changeip.php

> Authenticated attackers can execute arbitrary commands as the apache user by injecting shell metacharacters into the mtu_eth0 parameter in VA MAX.

- **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:** 5 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-gx46-63hv-r9x3

## What is CVE-2019-25671?

CVE-2019-25671 is a high-severity command injection vulnerability in VA MAX, published on 5 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VA MAX 8.3.4 contains a remote code execution vulnerability that allows authenticated attackers to execute arbitrary commands by injecting shell metacharacters into the mtu_eth0 parameter. Attackers can send POST requests to the changeip.php endpoint with malicious payload in the mtu_eth0 field to execute commands as the apache user.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2019-25671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25671 is a high-severity command injection vulnerability in VA MAX, published on 5 Apr 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-2019-25671 exists.

Affected product: VA MAX. 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-25671/ (Markdown: https://insights.sbomify.com/CVE-2019-25671/index.md)
```

## Sources

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

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