dbcve.org
Gx Works3Application · Mitsubishielectric

CVE-2022-29826

HIGH · 7.5 CVSS v3.1 Published 2022-11-25
Fix available
A fix is available. Upgrade to after 1.086q or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GX Works3 versions from 1.000A to 1.087R and Motion Control Setting(GX Works3 related software) versions from 1.000A to 1.042U allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated users may view programs and project files or execute programs illegally.

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

Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GX Works3 and Motion Control Setting software allows remote unauthenticated attackers to view programs, project files, and potentially execute programs illegally due to unencrypted storage of sensitive data.

MitigationImplement network segmentation and access controls to limit exposure; contact Mitsubishi Electric for patched versions; review and encrypt sensitive project files at rest where possible.

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
Gx Works3Application
Affected:>= 1.000a, <= 1.011m>= 1.015r, <= 1.086q

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed GX Works3 version
    Open GX Works3 and navigate to Help > Product Information, or check Programs and Features (Windows) for the installed version.
    Affected if The installed version falls within 1.000a through 1.011m, or 1.015r through 1.086q.
  2. Locate GX Works3 project files
    Search for project file extensions used by GX Works3 (typically .gx3, .gwx, or folder structures containing .mtw files) in the system.
    Affected if Project files exist and are stored in unencrypted locations accessible to unauthorized users.
  3. Verify project file storage security
    Inspect the directory permissions on project file folders. Check if files are stored on network shares, unencrypted drives, or locations with broad access permissions.
    Affected if Project files are stored without encryption and with weak or shared access controls.
  4. Check for sensitive data in project files
    Open a sample project file with a text editor or hex viewer to confirm whether sensitive information (IP addresses, credentials, proprietary logic) appears in cleartext within the file content.
    Affected if Sensitive data within project files is stored in cleartext rather than encrypted format.

A defender is affected if GX Works3 version is within the ranges 1.000a-1.011m or 1.015r-1.086q AND project files containing sensitive data are stored in unencrypted form with insufficient access controls.

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 a release after 1.086q
Interim mitigation

Implement network segmentation and access controls to limit exposure; contact Mitsubishi Electric for patched versions; review and encrypt sensitive project files at rest where possible.

Recommended fix High confidence

GX Works3 version 1.087S or later (or the latest stable release available from Mitsubishi Electric)

  1. 1. Identify the currently installed GX Works3 version by opening the software and checking 'Help' > 'Product Information' or the program's version properties
  2. 2. Download the fixed version of GX Works3 from the official Mitsubishi Electric download page: https://www.mitsubishielectric.com/fa/download/
  3. 3. Verify the downloaded installer matches the official file hashes provided on the download page
  4. 4. Create a complete backup of all existing GX Works3 project files, programs, and settings before proceeding with the upgrade
  5. 5. Close all running instances of GX Works3 and any related Mitsubishi Electric software
  6. 6. Run the installer with administrator privileges and follow the on-screen installation wizard prompts
  7. 7. After installation completes, verify the new version is 1.087S or higher by checking 'Help' > 'Product Information'
  8. 8. Test that existing project files can be opened and that project data is no longer stored in cleartext format
Caveat Minor: Some legacy project file formats from very old versions may require migration; verify project compatibility after upgrade

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

Fix this in Gx Works3 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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