CVE-2025-26410
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 · uneditedThe firmware of all Wattsense Bridge devices contain the same hard-coded user and root credentials. The user password can be easily recovered via password cracking attempts. The recovered credentials can be used to log into the device via the login shell that is exposed by the serial interface. The backdoor user has been removed in firmware BSP >= 6.4.1.
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 confidenceAll Wattsense Bridge devices contain hard-coded user and root credentials embedded in the firmware. The user password can be recovered through password cracking, and the recovered credentials allow authentication to the device via the serial interface login shell.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the device modelCheck the device label, web interface, or serial console output to confirm it is a Wattsense Bridge deviceAffected if Device is not a Wattsense Bridge product
-
Check the firmware BSP versionAccess the device web interface, check the system information page, or use the serial console to retrieve the current BSP firmware versionAffected if BSP version is earlier than 6.4.1 or version cannot be determined
-
Determine if serial interface is accessibleInspect the device hardware for exposed serial pins (TX, RX, GND) on the circuit board, or check if serial login is enabled in the device configurationAffected if Serial interface pins are present or serial login is enabled in configuration
-
Verify hard-coded credentials presenceExtract and analyze firmware image (if accessible) or consult Wattsense security advisory to confirm the backdoor credentials are embedded in the deployed firmware versionAffected if Firmware contains embedded credentials and serial access is available
You are affected if you have a Wattsense Bridge device running firmware BSP version earlier than 6.4.1 with an accessible serial interface that accepts the hard-coded 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 · scopedUpdate firmware to BSP version 6.4.1 or later to remove the hard-coded backdoor credentials.
Firmware BSP >= 6.4.1
- 1. Identify the current firmware version of the Wattsense Bridge device
- 2. Download the latest firmware BSP >= 6.4.1 from the official Wattsense support site (support.wattsense.com)
- 3. Follow the vendor's official firmware update procedure to apply the new firmware
- 4. After upgrade, verify that the hardcoded backdoor user has been removed
- 5. Change any default passwords if still present and use strong, unique credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26410 — 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-2025-26410 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