CVE-2020-7501
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 · uneditedA CWE-798: Use of Hard-coded Credentials vulnerability exists in Vijeo Designer Basic (V1.1 HotFix 16 and prior) and Vijeo Designer (V6.2 SP9 and prior) which could cause unauthorized read and write when downloading and uploading project or firmware into Vijeo Designer Basic and Vijeo Designer.
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 confidenceA hard-coded credentials vulnerability (CWE-798) exists in Vijeo Designer Basic (V1.1 HotFix 16 and prior) and Vijeo Designer (V6.2 SP9 and prior) that allows unauthorized read/write access during project and firmware download/upload operations. Attackers with knowledge of these embedded credentials can bypass authentication to modify industrial automation projects.
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<= 1.0<= 6.2= 1.1= 6.9CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Vijeo Designer installationCheck for Vijeo Designer or Vijeo Designer Basic in the system. Look in typical installation directories such as C:\Program Files\Schneider Electric\Vijeo Designer or C:\Program Files (x86)\Schneider Electric\Vijeo Designer. Also check the Windows Programs and Features list (Control Panel > Programs > Programs and Features).Affected if Vijeo Designer or Vijeo Designer Basic is installed on the system
-
Determine installed version numberOpen Vijeo Designer or Vijeo Designer Basic. Navigate to Help > About or look for a version info option in the application menu. Alternatively, check the executable file properties: right-click on VijeoDesigner.exe or VijeoDesignerBasic.exe, select Properties, then view the Details tab for Product Version.Affected if The installed version is Vijeo Designer Basic V1.1 HotFix 16 or prior, or Vijeo Designer V6.2 SP9 or prior
-
Verify project file access permissionsAttempt to open a Vijeo project file (.vjpr or similar extension) in the Vijeo Designer application. Check whether the application allows read/write access to the project without requiring authentication credentials.Affected if The application allows read or write access to project files without prompting for credentials, indicating the hard-coded credentials may be in use
-
Check firmware operation configurationWithin the Vijeo Designer application, access the firmware download/upload settings. Look for options related to PLC or device firmware operations and verify whether these operations proceed without requiring authentication.Affected if Firmware download/upload operations can be initiated or completed without authentication prompts, suggesting the vulnerability is present
The system is affected if Vijeo Designer Basic V1.1 HotFix 16 or prior, or Vijeo Designer V6.2 SP9 or prior is installed and the application allows unauthenticated project or firmware operations.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to Vijeo Designer Basic V1.1 HotFix 17 or later and Vijeo Designer V6.2 SP10 or later to obtain patched versions without hardcoded credentials; audit for any unauthorized access attempts.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7501 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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