CVE-2019-19095
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 adequate input/output validation for ABB eSOMS versions 4.0 to 6.0.2 might allow an attacker to attack such as stored cross-site scripting by storing malicious content in the 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 confidenceABB eSOMS versions 4.0 to 6.0.2 contain a stored cross-site scripting (XSS) vulnerability due to insufficient input validation and output encoding. Attackers can inject malicious JavaScript payloads into data fields that get stored in the database, which then executes when other users view or interact with the compromised content through the web 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>= 4.0, <= 6.0.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 if ABB eSOMS is installedCheck your system for the presence of ABB eSOMS application. This may be found in installed programs list, application directories, or by accessing the web interface URL commonly used by the product.Affected if ABB eSOMS or Hitachienergy Esoms software is present on the system
-
Determine installed versionLocate the version information for the installed ABB eSOMS instance. This is typically accessible through the web interface login page, about section, or system information panel within the application.Affected if The installed version is between 4.0 and 6.0.2 inclusive
-
Verify web interface is accessibleConfirm the eSOMS web interface is accessible by accessing the application's URL. Note the exposure level (internal network only or externally accessible).Affected if The web interface is reachable by users
-
Check for stored XSS in user input fieldsInspect data entry points in the application such as form fields, search inputs, comment fields, or any area where user-supplied data is stored and later displayed to other users. Review application logs for any suspicious script tags or XSS attempt indicators.Affected if User-supplied data in stored fields is rendered without proper encoding when viewed by other users
You are affected if ABB eSOMS or Hitachienergy Esoms version 4.0 through 6.0.2 is installed and the web interface is accessible, as the stored XSS vulnerability allows malicious scripts to execute in other users browsers.
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 dataUpgrade to a patched version of ABB eSOMS if available, or implement robust input validation combined with context-aware output encoding for all user-supplied data displayed in the application.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19095 — 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-19095 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