CVE-2026-42951
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 · uneditedAn authenticated user can download a backup of the Danelec MacGregor Voyage Data Recorder device which includes account data and password hashes.
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 confidenceAn authenticated user can download a backup file from the Danelec MacGregor Voyage Data Recorder that contains plaintext account data and password hashes, exposing user credentials through the backup mechanism.
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< 5.250CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device and firmware versionAccess the Danelec MacGregor VDR web interface or use SNMP/SSH to query the device. Look for firmware version information in the system status or about section. For command-line access, run: 'show version' or check /etc/version depending on available shell.Affected if The firmware version is Macgregor Interschalt Vdr G4e and is below 5.250.
-
Locate the backup download functionalityExamine the web interface for a backup, export, or system save feature. Common paths include /backup, /export, /system/backup, or a download button in settings. Check the HTTP responses when navigating admin or settings menus.Affected if A backup or export option exists and is accessible to authenticated users.
-
Verify backup contains sensitive dataIf you can obtain a backup file (from a test account or previous export), inspect its contents. Look for user account lists, password hashes, or credential-related fields within the backup archive.Affected if The backup file contains plaintext passwords, password hashes, or user credential data.
-
Test access control on backup featureCreate or use a non-administrator account (standard user or read-only role). Attempt to access and download the backup functionality using this account's credentials.Affected if A non-administrator authenticated user can successfully download the system backup.
You are affected if the device runs Macgregor Interschalt Vdr G4e firmware below version 5.250 and any authenticated user (not just administrators) can download a backup containing password hashes or credentials.
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.
dbcve · scoped5.250
Implement proper authorization controls to restrict backup downloads and ensure backup files exclude sensitive data or are encrypted.
Firmware version 5.250 or later
- Identify the current firmware version of the Interschalt Vdr G4e device by accessing the device management interface
- Obtain the firmware version 5.250 or later from Danelec MacGregor official support channels (www.danelec.com)
- Review the vendor's official firmware update documentation and release notes
- Apply the firmware upgrade following the vendor's documented procedure, typically via the device's web interface or maintenance port
- After upgrading, verify the vulnerability is remediated by attempting to download a backup and confirming credentials are properly protected/hashed
- Consult CISA (www.cisa.gov) for any additional advisory information or mitigation guidance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42951 — 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-2026-42951 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