dbcve.org
Sitesentinel Isite Atg FirmwareOperating system · Opwglobal

CVE-2017-12731

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-09
Fix available
A fix is available. Upgrade to after 175 or later.
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
A SQL Injection issue was discovered in OPW Fuel Management Systems SiteSentinel Integra 100, SiteSentinel Integra 500, and SiteSentinel iSite ATG consoles with the following software versions: older than V175, V175-V189, V191-V195, and V16Q3.1. The application is vulnerable to injection of malicious SQL queries via the input from the client.

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 OPW Fuel Management Systems SiteSentinel (Integra 100, Integra 500, iSite ATG consoles) allows remote attackers to inject malicious SQL queries through client-side input fields. The vulnerability affects multiple version ranges including V175-V189, V191-V195, and V16Q3.1.

MitigationUpgrade to vendor-provided patched version (V175 or later for older versions, V196+ for V191-V195, V16Q4+ for V16Q3.1). If immediate patching is not possible, implement input validation and parameterized queries at all application entry points as a compensating control.

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
Sitesentinel Isite Atg FirmwareOperating system
Affected:<= 175= 16q3.1= 189= 191= 195
Sitesentinel Integra 500 FirmwareOperating system
Affected:<= 175= 16q3.1= 189= 191= 195
Sitesentinel Integra 100 FirmwareOperating system
Affected:<= 175= 16q3.1= 189= 191= 195

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 the SiteSentinel firmware version
    Access the device web interface (typically at http://device_ip) and navigate to System Information or About page to view the firmware version. Alternatively, check the device console or documentation for version labeling.
    Affected if The firmware version matches V175-V189, V191-V195, V16Q3.1, or any version <= 175 (including 175), or equals exactly 189, 191, or 195.
  2. Confirm the device model is affected
    Verify the device is one of the following models: SiteSentinel Integra 100, Integra 500, or iSite ATG console. Check the product label or web interface system information for the model number.
    Affected if The device is any of these three models (Integra 100, Integra 500, or iSite ATG) running an affected firmware version.
  3. Determine if the web management interface is accessible
    Attempt to access the device IP address via HTTP/HTTPS from a permitted network location. Check if the login page or any web interface endpoints respond.
    Affected if The web interface is reachable over the network (even if behind authentication), as the SQL injection is exploited through client-side input fields in the web application.
  4. Identify SQL injection entry points
    Inspect the login and input forms on the web interface (typically username, password, or other data entry fields). The vulnerability exists in client-side input fields where SQL queries can be injected.
    Affected if The web interface contains input fields that do not use parameterized queries, allowing direct SQL syntax to be submitted.

Your environment is affected if you are running any SiteSentinel Integra 100, Integra 500, or iSite ATG console with firmware version V175 through V189, V191 through V195, V16Q3.1, or versions <= 175, and the device web interface 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
Upgrade available Upgrade to a release after 175
Interim mitigation

Upgrade to vendor-provided patched version (V175 or later for older versions, V196+ for V191-V195, V16Q4+ for V16Q3.1). If immediate patching is not possible, implement input validation and parameterized queries at all application entry points as a compensating control.

Fix this in Sitesentinel Isite Atg Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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