CVE-2013-0684
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 · uneditedSQL injection vulnerability in Invensys Wonderware Information Server (WIS) 4.0 SP1SP1, 4.5- Portal, and 5.0- Portal allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in Invensys Wonderware Information Server allows remote attackers to execute arbitrary SQL commands. The vulnerability affects versions 4.0 SP1, 4.5-Portal, and 5.0-Portal. Successful exploitation could allow attackers to read, modify, or delete database contents including potentially sensitive operational data.
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= 4.0= 4.5= 5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Wonderware Information Server installationCheck for the presence of Wonderware Information Server by looking for its installation directory, typically at C:\Program Files\Wonderware\Information Server or in the Windows installed programs list.Affected if The software is not found on the system, the user is not affected.
-
Determine installed versionOpen Windows Control Panel, go to Programs and Features, locate Wonderware Information Server, and note the version number shown in the Version column.Affected if The installed version is 4.0 SP1, 4.5 (Portal), or 5.0 (Portal), indicating the affected version.
-
Check if web portal interface is enabledLocate the Information Server configuration files or IIS settings to determine if the web portal component is actively running and accessible.Affected if The web portal is enabled and accessible, making the SQL injection vulnerability potentially exploitable.
-
Verify network exposureReview network configuration to determine if the Information Server web interface is accessible from outside the local network or from untrusted networks.Affected if The server is exposed to untrusted networks, increasing the likelihood of remote exploitation.
-
Inspect application logs for suspicious SQL activityCheck Wonderware Information Server logs for unusual database query patterns, especially in web access logs that may indicate SQL injection attempts.Affected if Suspicious SQL-like strings appear in logs, indicating potential exploitation attempts.
A user is affected if Wonderware Information Server versions 4.0 SP1, 4.5, or 5.0 are installed with the web portal enabled and exposed to network access.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement parameterized queries or prepared statements for all database interactions. Apply vendor-supplied patches if available, or upgrade to a supported version. Restrict network access to the Information Server to reduce exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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