Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

SQL injection in Advantech iView via SNMP v1 trap (UDP/162)

IdentifiersCVE-2025-13373CWE-89· Improper Neutralization of Special…

Advantech iView versions 5.7.05.7057 and earlier do not properly sanitize/neutralize input contained in SNMP v1 trap requests received on port 162. As a result, an unauthenticated remote attacker can craft SNMP v1 trap payloads that are incorporated into backend SQL queries, enabling SQL injection.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote, unauthenticated SQL injection that can be used to disclose sensitive information and to modify or delete data in the underlying database. CVSS v3.1 vector indicates high confidentiality impact with no integrity/availability impact (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), while advisory text also notes potential data modification/deletion.

Mitigation

If you can’t patch tonight, do this now.

Minimize exposure of iView by preventing direct Internet access; isolate control system networks behind firewalls; use secure remote access (e.g., VPN) and keep remote-access components patched/up to date, per CISA ICS defense-in-depth guidance.

Remediation

Patch, then assume compromise.

Upgrade Advantech iView to version 5.8.1 (vendor-fixed release) or later.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.