dbcve.org
Webaccess\/scadaApplication · Advantech

CVE-2019-6523

CRITICAL · 9.8 CVSS v3.0 Published 2019-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
WebAccess/SCADA, Version 8.3. The software does not properly sanitize its inputs for 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

SQL injection vulnerability in WebAccess/SCADA v8.3 due to improper input sanitization. Attackers can inject malicious SQL commands through unsanitized input fields, potentially allowing unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade to patched version if available; otherwise implement input validation, convert to parameterized queries, and apply network segmentation to limit exposure of the SCADA interface.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Webaccess\/scadaApplication
Affected:= 8.3

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
High
Availability
High

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

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. Identify if Advantech WebAccess/SCADA is installed
    Check for the presence of WebAccess/SCADA installation directories or services. Common installation paths include C:\Program Files\Advantech\WebAccess or C:\WebAccess. On Windows, check Services for 'Advantech WebAccess' or 'WebAccess' services.
    Affected if Advantech WebAccess/SCADA software is present on the system
  2. Determine installed version of WebAccess/SCADA
    Locate version information in the installation directory, typically in a version.ini, about.txt, or in the Windows Registry under HKLM\SOFTWARE\Advantech\WebAccess. The web interface login page may also display the version.
    Affected if Installed version is exactly 8.3
  3. Check if the SCADA web interface is network accessible
    Verify if TCP ports used by WebAccess (commonly port 80, 443, or 8080) are listening and accessible from network segments. Use netstat -an or port scanning to confirm.
    Affected if The web interface is exposed on the network and accepts user input through web forms

Environment is affected if Advantech WebAccess/SCADA version 8.3 is installed and its web interface with user input fields is network-accessible.

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

Upgrade to patched version if available; otherwise implement input validation, convert to parameterized queries, and apply network segmentation to limit exposure of the SCADA interface.

Fix this in Webaccess\/scada Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6523 — 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-2019-6523 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