dbcve.org
CscapeApplication · Hornerautomation

CVE-2023-7206

HIGH · 7.8 CVSS v3.1 Published 2024-01-15
Fix available
A fix is available. Upgrade to 9.90 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
In Horner Automation Cscape versions 9.90 SP10 and prior, local attackers are able to exploit this vulnerability if a user opens a malicious CSP file, which would result in execution of arbitrary code on affected installations of Cscape.

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 file-parsing vulnerability in Horner Automation Cscape industrial programming software. A local attacker crafts a malicious CSP project file that, when opened by a user, triggers arbitrary code execution through improper handling of file contents during the parsing process.

MitigationDo not open CSP files from untrusted or unknown sources. Update to a patched version of Cscape when released by the vendor. Implement application whitelisting and endpoint detection tools to block malicious file execution.

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
CscapeApplication
Affected:< 9.90= 9.90

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. Identify if Cscape is installed
    Look for Horner Automation Cscape in the system program directory, or check installed programs via Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Cscape*'}
    Affected if The software is not found on the system, then this CVE does not apply.
  2. Determine the installed Cscape version
    Right-click the Cscape executable (commonly in C:\Program Files\Horner Automation\Cscape\ or C:\Program Files (x86)\Horner Automation\Cscape\), select Properties, and check the Details tab for the File Version or Product Version.
    Affected if The version is 9.90 or lower (anything below 9.90 or exactly 9.90).
  3. Check for CSP file usage
    Search the system for .CSP project files, or review workflows where Cscape is used to open project files received from external sources or stored in shared locations.
    Affected if Users open or process CSP files with this version of Cscape, creating the conditions for exploitation.

If Horner Automation Cscape version 9.90 or lower is installed and users open CSP project files with it, the environment is affected by this 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.

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

Do not open CSP files from untrusted or unknown sources. Update to a patched version of Cscape when released by the vendor. Implement application whitelisting and endpoint detection tools to block malicious file execution.

Recommended fix Moderate confidence

Cscape version newer than 9.90 SP10 (contact Horner Automation for exact fixed release)

  1. 1. Navigate to the official Horner Automation website or their support portal to obtain the latest Cscape software version.
  2. 2. Download the most recent version of Cscape that is newer than version 9.90 SP10.
  3. 3. Ensure all work is saved and close any running instances of Cscape.
  4. 4. Install the new version of Cscape, following the vendor's installation instructions.
  5. 5. After installation, verify the version number in the software to confirm the upgrade was successful.
  6. 6. If available, review release notes for security updates to confirm the vulnerability is addressed.
Caveat Review release notes for any changes to project file compatibility or functionality

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

Fix this in Cscape Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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