Exacqvision Enterprise ManagerApplication · Johnsoncontrols

CVE-2021-27658

MEDIUM · 5.4 CVSS v3.1 Published 2021-06-24
Fix available
A fix is available. Upgrade to after 20.12 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
exacqVision Enterprise Manager 20.12 does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users.

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

exacqVision Enterprise Manager 20.12 contains a cross-site scripting (XSS) vulnerability where user-supplied input is not properly validated, filtered, escaped, or encoded before being rendered in web pages served to other users. This allows authenticated attackers to inject malicious JavaScript or HTML into web interfaces.

MitigationImplement context-aware output encoding and input validation for all user-controllable fields in the web application. Consider deploying Content Security Policy (CSP) headers as an additional defense-in-depth measure.

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
Exacqvision Enterprise ManagerApplication
Affected:<= 20.12

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
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 checks

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

  1. Identify if exacqVision Enterprise Manager is installed
    Look for the exacqVision Enterprise Manager service or application in your system. Check for installation directories typically under C:\Program Files\exacqVision\Enterprise Manager or /opt/exacqvision/ on Linux systems.
    Affected if The application is present on the system
  2. Determine the installed version of exacqVision Enterprise Manager
    Open the Enterprise Manager application and navigate to Help > About, or check the version in the installed software list (Windows Add/Remove Programs, Linux package manager). Compare the version number to 20.12.
    Affected if The installed version is 20.12 or any earlier version (<= 20.12)
  3. Verify the web interface is accessible
    Access the Enterprise Manager web interface by navigating to https://localhost:8081 or the configured server address in a web browser. Confirm the login page loads.
    Affected if The web interface is reachable and accepts authentication
  4. Confirm authentication is enabled for the web interface
    Check the Enterprise Manager server configuration to ensure user authentication is not disabled. Attempt to log in with valid credentials or check authentication settings in the admin panel.
    Affected if Authentication is enabled and user accounts exist in the system

If exacqVision Enterprise Manager is installed with version 20.12 or earlier and the web interface is accessible with authentication enabled, the environment is affected by this XSS vulnerability.

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

Implement context-aware output encoding and input validation for all user-controllable fields in the web application. Consider deploying Content Security Policy (CSP) headers as an additional defense-in-depth measure.

Fix this in Exacqvision Enterprise Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-27658 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