dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13373

HIGH · 7.5 CVSS v3.1 Published 2025-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Advantech iView versions 5.7.05.7057 and prior contain an SQL injection vulnerability in the SNMP v1 trap handler (port 162). The application fails to sanitize SNMP trap data before using it in SQL queries, allowing remote attackers to inject arbitrary SQL commands through specially crafted SNMP trap messages.

MitigationApply the vendor patch when available. Until then, network-segment the affected system and restrict access to UDP port 162. Implement input validation on SNMP trap data before database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Advantech iView is installed
    Check for Advantech iView in installed programs (Windows Control Panel > Programs and Features) or look for iView processes running on the system using Task Manager or 'tasklist' command
    Affected if Advantech iView software is found on the system
  2. Identify the installed version
    Right-click the iView application shortcut or executable, select Properties, and check the Details tab for version information, or check the program's about/help section
    Affected if The version number is 5.7.05.7057 or lower (e.g., 5.7.04, 5.7.03, etc.)
  3. Verify SNMP Trap Receiver service is enabled
    Check if the SNMP Trap service is running by opening Services (services.msc) and looking for 'SNMP Trap' service, or run 'netsh interface show udpportstats' or check firewall rules for UDP port 162
    Affected if SNMP Trap service is running or UDP port 162 is open/listening on the system
  4. Confirm iView is configured to receive SNMP traps
    Access iView administration interface and check SNMP settings to verify trap reception is enabled, or examine iView configuration files for SNMP trap receiver settings
    Affected if iView is configured to accept and process SNMP v1 traps

A system is affected if it runs Advantech iView version 5.7.05.7057 or prior with the SNMP Trap service enabled and configured to receive traps on UDP port 162.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available. Until then, network-segment the affected system and restrict access to UDP port 162. Implement input validation on SNMP trap data before database queries.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13373 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13373 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data