dbcve.org
X Stream Enhanced Xegp FirmwareOperating system · Emerson

CVE-2021-27465

MEDIUM · 6.1 CVSS v3.1 Published 2021-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 vulnerability has been found in multiple revisions of Emerson Rosemount X-STREAM Gas Analyzer. The affected applications do not validate webpage input, which could allow an attacker to inject arbitrary HTML code into a webpage. This would allow an attacker to modify the page and display incorrect or undesirable data.

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 confidence

This is a reflected HTML injection vulnerability in the web interface of Emerson Rosemount X-STREAM Gas Analyzer. The application's input fields do not properly validate or sanitize user-supplied data before rendering it in HTML context, allowing an attacker to inject arbitrary HTML code. This can be exploited to manipulate page content displayed to users, potentially leading to phishing or display of deceptive data.

MitigationImplement proper input validation and output encoding across all web application input points to neutralize HTML/JavaScript injection attempts. Since this is an embedded industrial device, coordinate with the vendor for official firmware patches and follow their update procedures.

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
X Stream Enhanced Xegp FirmwareOperating system
Affected:all versions
X Stream Enhanced Xegk FirmwareOperating system
Affected:all versions
X Stream Enhanced Xefd FirmwareOperating system
Affected:all versions
X Stream Enhanced Xexf FirmwareOperating system
Affected:all versions

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the web interface login page or device status page. Look for the model designation (Xegp, Xegk, Xefd, or Xexf) displayed in the header, footer, or device information section. Alternatively, check physical device labeling or network discovery documentation.
    Affected if The device model is Xegp, Xegk, Xefd, or Xexf (any firmware version).
  2. Confirm the firmware version
    In the web interface, navigate to the System Info, About, or Diagnostics page to view the installed firmware version. Note that according to the CVE, all firmware versions are affected.
    Affected if Any firmware version is installed on one of the affected models.
  3. Verify the web interface is enabled
    Attempt to access the device web interface via HTTP/HTTPS on the configured port (typically 80 or 443, or a custom port). Confirm the login page or device status page loads.
    Affected if The web interface is accessible and responsive.
  4. Identify injectable input fields
    Log into the web interface and browse available input fields in configuration forms, user settings, device naming, or diagnostic input areas. Common targets include device name, description fields, or any user-configurable text inputs.
    Affected if The web interface contains text input fields that accept user-supplied data.
  5. Test for HTML injection
    Enter a simple HTML test payload such as <b>test</b> or <script>alert(1)</script> into a text input field and submit. Then view the page source or inspect the rendered output to see if the HTML tags appear unescaped or are executed.
    Affected if The submitted HTML tags are rendered as-is in the response without encoding or sanitization, confirming the injection vulnerability.

The environment is affected if the device is an Emerson X-Stream Enhanced model (Xegp, Xegk, Xefd, or Xexf) with an accessible web interface where input fields reflect unescaped HTML characters back to the user.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding across all web application input points to neutralize HTML/JavaScript injection attempts. Since this is an embedded industrial device, coordinate with the vendor for official firmware patches and follow their update procedures.

Fix this in X Stream Enhanced Xegp Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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