dbcve.org
Proface Gp Pro Ex Ex EdApplication · Schneider Electric

CVE-2015-7921

CRITICAL · 9.1 CVSS v3.1 Published 2016-04-06
Fix available
A fix is available. Upgrade to after 4.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The FTP server in Pro-face GP-Pro EX EX-ED before 4.05.000, PFXEXEDV before 4.05.000, PFXEXEDLS before 4.05.000, and PFXEXGRPLS before 4.05.000 has hardcoded credentials, which makes it easier for remote attackers to bypass authentication by leveraging knowledge of these credentials.

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

The FTP server in Pro-face GP-Pro EX (multiple product variants EX-ED, PFXEXEDV, PFXEXEDLS, PFXEXGRPLS) contains hardcoded credentials embedded in the software. Attackers with knowledge of these credentials can bypass authentication entirely and gain unauthorized remote access to the FTP server, potentially allowing file access or further compromise of the HMI system.

MitigationUpgrade to GP-Pro EX version 4.05.000 or later as the vendor has patched the hardcoded credential issue. Additionally, restrict network access to the FTP port and monitor for unauthorized access attempts.

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
Proface Gp Pro Ex Ex EdApplication
Affected:<= 4.0.4
Proface Gp Pro Ex PfxexedlsApplication
Affected:<= 4.0.4
Proface Gp Pro Ex PfxexedvApplication
Affected:<= 4.0.4
Proface Gp Pro Ex PfxexgrplsApplication
Affected:<= 4.0.4

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 GP-Pro EX product variant
    Check the installed software on the system for any of these product names: EX-ED, PFXEXEDLS, PFXEXEDV, PFXEXGRPLS. Look in Add/Remove Programs (Windows) or the program's installation directory for product identification files or registry entries.
    Affected if Any of these product variants are installed on the system
  2. Determine installed software version
    Locate the GP-Pro EX installation and check the version. Common locations: Program Files folder under Pro-face or Schneider Electric, or check version info in the software's About/Help menu if the application is accessible.
    Affected if The installed version is 4.0.4 or earlier (any version <= 4.0.4)
  3. Check if FTP server component is enabled
    Examine the GP-Pro EX configuration for FTP server settings. The FTP server is typically configured within the HMI project settings or runtime configuration. Look for FTP service enablement in project files or runtime configuration panels.
    Affected if The FTP server feature is enabled or configured in the GP-Pro EX environment

The environment is affected if GP-Pro EX variant EX-ED, PFXEXEDLS, PFXEXEDV, or PFXEXGRPLS is installed with version 4.0.4 or earlier AND the FTP server component is enabled.

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 4.0.4
Interim mitigation

Upgrade to GP-Pro EX version 4.05.000 or later as the vendor has patched the hardcoded credential issue. Additionally, restrict network access to the FTP port and monitor for unauthorized access attempts.

Recommended fix High confidence

GP-Pro EX version 4.05.000 or later (for all affected variants: EX-ED, PFXEXEDV, PFXEXEDLS, PFXEXGRPLS)

  1. Identify the specific Pro-face GP-Pro EX product variant (EX-ED, PFXEXEDV, PFXEXEDLS, or PFXEXGRPLS) currently installed
  2. Navigate to the official Pro-face support website or contact Pro-face technical support to obtain version 4.05.000 or later of the affected product
  3. Backup all existing project files, configurations, and data before performing the upgrade
  4. Download the updated GP-Pro EX version 4.05.000 or newer for your specific product variant
  5. Install the new version following Pro-face's standard installation procedures
  6. After upgrade, verify that the FTP server no longer uses the hardcoded credentials
  7. Change any default passwords that may still exist and implement strong, unique credentials for FTP access
  8. Test that legitimate FTP functionality works correctly with the new credentials

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

Fix this in Proface Gp Pro Ex Ex Ed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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