dbcve.org
Cx ProgrammerApplication · Omron

CVE-2022-25230

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 9.77 or later.
See remediation →
81/100
Remediation priority · High
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
Use after free vulnerability in CX-Programmer v9.76.1 and earlier which is a part of CX-One (v4.60) suite allows an attacker to cause information disclosure and/or arbitrary code execution by having a user to open a specially crafted CXP file. This vulnerability is different from CVE-2022-25325.

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

Use-after-free vulnerability in CX-Programmer v9.76.1 and earlier (CX-One v4.60 suite) that triggers when parsing a specially crafted CXP file. Successful exploitation allows an attacker to achieve information disclosure and/or arbitrary code execution through a malformed file opened by the victim.

MitigationAvoid opening untrusted CXP files; apply vendor patch when available; consider network segmentation and user training to reduce exposure to malicious file delivery vectors.

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
Cx ProgrammerApplication
Affected:< 9.77

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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. Confirm CX-Programmer is installed
    Check the program directory (typically C:\Program Files\Omron\CX-Programmer) or look for CX-Programmer in the Windows Start Menu and installed programs list
    Affected if CX-Programmer is present on the system
  2. Identify the installed CX-Programmer version
    Open CX-Programmer, go to Help > About CX-Programmer, or right-click the executable in the installation folder and select Properties > Details to view the File Version
    Affected if The displayed version is 9.76.1 or earlier, or any version below 9.77
  3. Check CX-One suite version if CX-Programmer came from that bundle
    If installed as part of CX-One, open CX-One Launcher and check the suite version displayed, or look for version info in the CX-One installation directory
    Affected if The CX-One suite version is 4.60 or earlier and includes an affected CX-Programmer version
  4. Verify file association with CXP files
    Check if .cxp file extension is associated with CX-Programmer by right-clicking any .cxp file and viewing 'Opens with', or check Registry under HKEY_CLASSES_ROOT\.cxp
    Affected if CXP files are configured to open with CX-Programmer, enabling the parsing attack surface

The system is affected if CX-Programmer version is 9.76.1 or earlier (below 9.77) and the software is used to open CXP 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
Upgrade available Upgrade to 9.77 or later
Fixed in 9.77
Interim mitigation

Avoid opening untrusted CXP files; apply vendor patch when available; consider network segmentation and user training to reduce exposure to malicious file delivery vectors.

Recommended fix High confidence

CX-Programmer 9.77 or later (part of CX-One v4.61 or later)

  1. 1. Back up all current CX-Programmer project files and configurations before upgrading.
  2. 2. Uninstall the current version of CX-Programmer from the system.
  3. 3. Download CX-Programmer version 9.77 or later from the official Omron website (cx-one.com) or through the CX-One suite installer.
  4. 4. Install CX-Programmer version 9.77 or later following the installation wizard prompts.
  5. 5. After installation, verify the installed version by opening CX-Programmer and checking Help > About CX-Programmer to confirm version 9.77 or higher is installed.
  6. 6. Test critical project files to ensure compatibility with the upgraded version.
Caveat Minor version upgrades typically retain compatibility with existing project files; however, test critical configurations before production use

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

Fix this in Cx Programmer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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