dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-11774

HIGH · 8.2 CVSS v3.1 Published 2025-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High

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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the software keyboard function (hereinafter referred to as "keypad function") of Mitsubishi Electric GENESIS64 versions 10.97.2 CFR3 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.2 CFR3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.2 CFR3 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97.2 CFR3 and prior, Mitsubishi Electric MobileHMI versions 10.97.2 CFR3 and prior, Mitsubishi Electric Iconics Digital Solutions MobileHMI versions 10.97.2 CFR3 and prior, and Mitsubishi Electric MC Works64 all versions allows a local attacker to execute arbitrary executable files (EXE) when a legitimate user uses the keypad function by tampering with the configuration file for the function. This could allow the attacker to disclose, tamper with, delete, or destroy information stored on the PC where the affected product is installed, or cause a denial-of-service (DoS) condition on the system, through the execution of the EXE.

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 an OS Command Injection vulnerability in the software keyboard (keypad) function of Mitsubishi Electric GENESIS64 and related products (ICONICS Suite, MobileHMI, MC Works64). A local attacker can tamper with the configuration file for the keypad function to execute arbitrary executable files (EXE) when a legitimate user uses the function, potentially leading to information disclosure, tampering, deletion, or destruction of data, or denial of service.

MitigationApply the vendor-provided patch or update to GENESIS64 to a version beyond 10.97.2 CFR3. Review and secure configuration files for the keypad function to prevent unauthorized tampering, and limit local access to affected systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

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 installed GENESIS64 or ICONICS Suite version
    Open the application or check the program files for the version information, typically found in the software's About or Help section, or in the Windows Programs and Features list
    Affected if The installed version is 10.97.2 CFR3 or earlier, as versions prior to the patch contain the vulnerability
  2. Locate keypad function configuration files
    Search for configuration files related to the software keyboard or keypad feature within the GENESIS64 or ICONICS installation directory
    Affected if Keypad configuration files exist and are present in the installation directory, indicating the vulnerable component is installed
  3. Verify configuration file permissions
    Check file system permissions on the keypad configuration files to determine if unauthorized local users can modify them
    Affected if Configuration files are writable by users other than administrators, allowing potential tampering
  4. Confirm keypad function is enabled
    Review the software settings or HMI configuration to determine if the keypad/keyboard function is actively enabled for use
    Affected if The keypad function is enabled and available for use in the application, making the vulnerability reachable

A system is affected if it runs GENESIS64, ICONICS Suite, MobileHMI, or MC Works64 version 10.97.2 CFR3 or earlier with the keypad function enabled and accessible configuration files.

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

Apply the vendor-provided patch or update to GENESIS64 to a version beyond 10.97.2 CFR3. Review and secure configuration files for the keypad function to prevent unauthorized tampering, and limit local access to affected systems.

Recommended fix Moderate confidence

Mitsubishi Electric GENESIS64/ICONICS Suite/MobileHMI version > 10.97.2 CFR3 (contact vendor for exact fixed release)

  1. Identify the specific product and version of GENESIS64, ICONICS Suite, MobileHMI, or MC Works64 currently installed
  2. Navigate to Mitsubishi Electric's official support page or contact their technical support to obtain the security patch or updated version
  3. Upgrade to a version newer than 10.97.2 CFR3 (e.g., 10.97.3 or later) that addresses this vulnerability
  4. After upgrading, verify that the keypad function configuration files are properly secured with appropriate file permissions
  5. Test the keypad function to confirm it operates correctly with the updated software
Caveat Review release notes for any compatibility changes or functionality updates in the new version before deployment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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