dbcve.org
MobilehmiApplication · Iconics

CVE-2022-23127

MEDIUM · 6.1 CVSS v3.1 Published 2022-01-21
Fix available
A fix is available. Upgrade to 10.95.210.01 or later.
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
Cross-site Scripting vulnerability in Mitsubishi Electric MC Works64 versions 4.04E (10.95.210.01) and prior and ICONICS MobileHMI versions 10.96.2 and prior allows a remote unauthenticated attacker to gain authentication information of an MC Works64 or MobileHMI and perform any operation using the acquired authentication information, by injecting a malicious script in the URL of a monitoring screen delivered from the MC Works64 server or MobileHMI server to an application for mobile devices and leading a legitimate user to access this URL.

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 Cross-Site Scripting (XSS) vulnerability in MC Works64 and ICONICS MobileHMI web applications. An unauthenticated remote attacker can inject malicious JavaScript into URL parameters of monitoring screens, which then executes in the victim's browser when they access the crafted URL, allowing theft of authentication credentials such as session cookies or tokens.

MitigationImplement proper input validation and output encoding for all URL parameters, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution. Users should avoid clicking untrusted links until vendor patches are applied.

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
MobilehmiApplication
Affected:<= 10.96.2
Mc Works64Application
Affected:< 10.95.210.01

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 if Iconics MobileHMI is installed
    Locate the Iconics MobileHMI installation directory and check the product version information, typically found in the application's about section, installer logs, or version file within the program files directory
    Affected if The installed version is 10.96.2 or lower
  2. Identify if Mitsubishi Electric MC Works64 is installed
    Locate the MC Works64 installation directory and check the product version information, typically found in the application's about section, installer logs, or version file within the program files directory
    Affected if The installed version is earlier than 10.95.210.01
  3. Confirm web interface is accessible
    Attempt to access the web-based monitoring interface by navigating to the application's URL endpoint in a browser or using a tool like curl to check if the web service responds
    Affected if The web interface is reachable over the network (internal or external)
  4. Verify URL parameter handling
    Inspect the application's monitoring screen URLs and test whether special characters in URL parameters are reflected back in the response without proper encoding
    Affected if URL parameters are reflected in the response without sanitization or encoding

A user is affected if either Iconics MobileHMI version 10.96.2 or below, or Mitsubishi Electric MC Works64 version below 10.95.210.01 is installed and the web-based monitoring interface is accessible and reflects URL parameters unsanitized.

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.

dbcve · scoped
Upgrade available Upgrade to 10.95.210.01 or later
Fixed in 10.95.210.01
Interim mitigation

Implement proper input validation and output encoding for all URL parameters, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution. Users should avoid clicking untrusted links until vendor patches are applied.

Recommended fix Moderate confidence

MC Works64: 4.04F (10.95.210.02) or later; MobileHMI: 10.96.3 or later

  1. 1. Identify the currently installed version of Mitsubishi Electric MC Works64 or ICONICS MobileHMI
  2. 2. For MC Works64: Upgrade to version 4.04F (10.95.210.02) or later to resolve the XSS vulnerability
  3. 3. For MobileHMI: Upgrade to version 10.96.3 or later to resolve the XSS vulnerability
  4. 4. After upgrading, verify the fix by checking that the monitoring screen URL parameters are properly sanitized and do not execute injected scripts
  5. 5. Consider implementing additional input validation at the web application firewall (WAF) level as a temporary mitigation if immediate upgrade is not feasible
Caveat Review release notes for any configuration changes required after upgrade; test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mobilehmi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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