dbcve.org
Control Fpwin ProApplication · Panasonic

CVE-2023-28729

HIGH · 7.8 CVSS v3.1 Published 2023-07-21
Fix available
A fix is available. Upgrade to after 7.6.0.3 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
A type confusion vulnerability in Panasonic Control FPWIN Pro versions 7.6.0.3 and all previous versions may allow arbitrary code execution when opening specially crafted project files.

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

A type confusion vulnerability in Panasonic Control FPWIN Pro versions 7.6.0.3 and earlier allows arbitrary code execution when a user opens a specially crafted malicious project file. The vulnerability stems from improper type handling during project file parsing, enabling an attacker to achieve code execution on the targeted system.

MitigationAvoid opening project files from untrusted sources; apply vendor patches when released; implement endpoint protection and file sandboxing for engineering workstation environments running this software.

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
Control Fpwin ProApplication
Affected:<= 7.6.0.3

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. Locate Panasonic Control FPWIN Pro installation
    Search for FPWIN Pro installation directories or check common program installation paths (C:\Program Files\Panasonic or C:\Program Files (x86)\Panasonic)
    Affected if The software is installed on the system
  2. Determine installed version
    Check the version information of the FPWIN Pro executable (usually fpwinpro.exe) by right-clicking the file, selecting Properties, and viewing the Details tab, or use PowerShell: Get-ChildItem -Path 'C:\Program Files*\Panasonic' -Recurse -Filter 'fpwinpro.exe' | Select-Object FullName, VersionInfo
    Affected if Unable to determine version or version cannot be verified
  3. Compare version to affected range
    Compare your installed version number to the affected range: versions 7.6.0.3 and earlier are vulnerable
    Affected if Installed version is 7.6.0.3 or earlier, or version cannot be determined but software is present
  4. Assess exposure to malicious project files
    Review recent usage of project files (.ppx or similar project file extensions used by FPWIN Pro) and check if files from untrusted or external sources have been opened recently
    Affected if The software is actively used and may open project files from untrusted sources

A user is affected if Panasonic Control FPWIN Pro is installed with version 7.6.0.3 or earlier, as the vulnerability triggers when opening specially crafted malicious project 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 a release after 7.6.0.3
Interim mitigation

Avoid opening project files from untrusted sources; apply vendor patches when released; implement endpoint protection and file sandboxing for engineering workstation environments running this software.

Recommended fix Moderate confidence

Latest version of Control FPWIN Pro newer than 7.6.0.3 (obtain exact version from Panasonic's official download page)

  1. Navigate to the official Panasonic industrial automation website (industry.panasonic.eu)
  2. Locate the Control FPWIN Pro software download section
  3. Download the latest version of Control FPWIN Pro that is newer than version 7.6.0.3
  4. Uninstall the current version of Control FPWIN Pro (if installed)
  5. Install the new version following the installation wizard prompts
  6. Verify the installed version matches the patched release
  7. Do not open untrusted or unsolicited project files in Control FPWIN Pro as a general security practice
Caveat Review release notes for any compatibility or feature changes between your current version and the new version

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

Fix this in Control Fpwin Pro 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-2023-28729 — 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-28729 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