dbcve.org
CsworksApplication · Controlsystemworks

CVE-2014-2351

HIGH · 7.5 CVSS v2.0 Published 2014-05-20
Fix available
A fix is available. Upgrade to after 2.5.5050.0 or later.
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
SQL injection vulnerability in the LiveData service in CSWorks before 2.5.5233.0 allows remote attackers to execute arbitrary SQL commands via vectors related to pathnames contained in web API requests.

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 the LiveData service of CSWorks (a SCADA/HMI software) allows remote attackers to inject arbitrary SQL commands through unsanitized pathname parameters in web API requests. The vulnerability exists because user-controlled input is directly concatenated into SQL queries without proper input validation or parameterized queries.

MitigationUpgrade CSWorks to version 2.5.5233.0 or later. If immediate patching is not possible, implement strict input validation on all pathname parameters in web API requests and refactor SQL queries to use parameterized queries/prepared statements.

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
CsworksApplication
Affected:<= 2.5.5050.0= 1.0.601.0= 1.0.612.0= 1.0.623.0= 1.0.720.0= 1.0.801.0= 1.0.813.0= 1.0.901.0= 1.0.3540.0= 1.0.3560.0= 1.0.3580.0= 1.1.3600.0

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 CSWorks installation and version
    Locate the CSWorks installation directory and find the version information. Common locations include the installation folder containing Csworks.dll or a version manifest file. Check the 'About' or version details in the CSWorks application if accessible.
    Affected if The installed version matches any of these: <= 2.5.5050.0; = 1.0.601.0; = 1.0.612.0; = 1.0.623.0; = 1.0.720.0; = 1.0.801.0; = 1.0.813.0; = 1.0.901.0; = 1.0.3540.0; = 1.0.3560.0; = 1.0.3580.0; = 1.1.3600.0
  2. Verify LiveData service is running
    Check if the CSWorks LiveData service is running on the system. This can be done through Windows Services (services.msc) looking for a service named 'CSWorks LiveData' or through command line: sc query CsworksLiveData or Get-Service -Name CsworksLiveData.
    Affected if The LiveData service is installed and running, exposing the vulnerable web API endpoint.
  3. Confirm web API accessibility
    Attempt to access the CSWorks web API endpoints. The LiveData service typically exposes HTTP endpoints. Check if port 8081 or the configured web service port is open and responding. Use a browser or curl to request the base web API URL.
    Affected if The web API is accessible over the network, meaning pathname parameters could be injected with malicious SQL commands.
  4. Inspect SQL query handling
    If source code or configuration is accessible, examine how pathname parameters from web API requests are handled. Look for SQL query construction that directly concatenates user input without parameterized queries. Check the LiveData service configuration files for SQL connection settings.
    Affected if SQL queries are constructed by directly concatenating pathname parameters without input validation or parameterized queries.

You are affected if the installed CSWorks version matches any of the affected versions listed AND the LiveData web API service is accessible over the network, allowing external injection of SQL commands through pathname parameters.

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 2.5.5050.0
Interim mitigation

Upgrade CSWorks to version 2.5.5233.0 or later. If immediate patching is not possible, implement strict input validation on all pathname parameters in web API requests and refactor SQL queries to use parameterized queries/prepared statements.

Fix this in Csworks Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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