# CVE-2025-13373: Advantech iView SQL Injection

> Attackers can inject SQL commands via SNMP trap requests in Advantech iView, potentially reading or modifying database contents.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-3w9v-5hv6-vvfx

## What is CVE-2025-13373?

CVE-2025-13373 is a high-severity SQL injection vulnerability in Advantech iView, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Advantech iView versions 5.7.05.7057 and prior do not properly sanitize SNMP v1 trap (Port 162) requests, which could allow an attacker to inject SQL commands.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-13373 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13373 is a high-severity SQL injection vulnerability in Advantech iView, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13373 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-13373/ (Markdown: https://insights.sbomify.com/CVE-2025-13373/index.md)
```

## Sources

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

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