# CVE-2025-52459: Advantech iView Argument Injection

> Authenticated attackers can inject arguments into backup commands to disclose sensitive database credentials in Advantech iView.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 10 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-5fcw-f94j-49qx

## What is CVE-2025-52459?

CVE-2025-52459 is a high-severity command injection vulnerability in Advantech iView, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability exists in Advantech iView that allows for argument 
injection in NetworkServlet.backupDatabase(). This issue requires an 
authenticated attacker with at least user-level privileges. Certain 
parameters can be used directly in a command without proper 
sanitization, allowing arbitrary arguments to be injected. This can 
result in information disclosure, including sensitive database 
credentials.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2025-52459?


## How do I fix CVE-2025-52459?

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

## Is CVE-2025-52459 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52459 and fix it if it is affected.

What it is: CVE-2025-52459 is a high-severity command injection vulnerability in Advantech iView, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52459 in the wild and no public exploit code.

Affected product: Advantech iView. 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-2025-52459/ (Markdown: https://insights.sbomify.com/CVE-2025-52459/index.md)
```

## Sources

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

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