CVE-2019-19094
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 · uneditedLack of input checks for SQL queries in ABB eSOMS versions 3.9 to 6.0.3 might allow an attacker SQL injection attacks against the backend database.
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 · high confidenceSQL injection vulnerability in ABB eSOMS versions 3.9 through 6.0.3 due to insufficient input validation on SQL queries. An authenticated or unauthenticated attacker could inject malicious SQL statements through user-supplied input to manipulate the backend database, potentially exposing sensitive data or compromising database integrity.
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>= 3.9, <= 6.0.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
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.
-
Identify eSOMS installation versionLocate the installed version of ABB eSOMS / Hitachienergy Esoms in the application's about page, system information panel, or version configuration file. Common locations include the web portal's footer, admin panel, or installation documentation.Affected if The installed version is 3.9, 4.x, 5.x, or 6.0.0 through 6.0.3 (any version from 3.9 through 6.0.3 inclusive)
-
Compare version to affected rangeVerify whether the identified version falls within the affected range of >= 3.9 and <= 6.0.3. If the version is below 3.9 or above 6.0.3, the specific flaw is not present.Affected if Version is >= 3.9 AND <= 6.0.3
-
Confirm web interface is accessibleDetermine if the eSOMS web application is network-accessible. SQL injection via user-supplied input typically targets web input fields such as login forms, search parameters, or data entry fields.Affected if The web interface is exposed and accepts user input through query parameters, form fields, or API endpoints
-
Check authentication configurationReview whether the application or specific endpoints allow unauthenticated access. The vulnerability note states both authenticated and unauthenticated attackers could exploit this flaw.Affected if The application permits unauthenticated access to interfaces that accept user input, or if default/admin credentials are in use
Your environment is affected if eSOMS version is 3.9 through 6.0.3 and the web interface accepting user input is accessible, regardless of authentication status.
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 dataApply vendor patch or upgrade to a version beyond 6.0.3. As a compensating control, implement parameterized queries and input validation until the vendor patch can be applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19094 — 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-2019-19094 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