dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-26411

HIGH · 8.8 CVSS v3.1 Published 2025-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An authenticated attacker is able to use the Plugin Manager of the web interface of the Wattsense Bridge devices to upload malicious Python files to the device. This enables an attacker to gain remote root access to the device. An attacker needs a valid user account on the Wattsense web interface to be able to conduct this attack. This issue is fixed in recent firmware versions BSP >= 6.1.0.

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

Authenticated attackers with valid web interface credentials can exploit insufficient validation in the Plugin Manager to upload malicious Python files, achieving remote root access on Wattsense Bridge devices.

MitigationUpgrade firmware to BSP >= 6.1.0 and enforce least-privilege access controls on web interface accounts to limit plugin upload capabilities.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Wattsense Bridge
    Access the web interface or check the device label/serial number to identify the device model
    Affected if Device is a Wattsense Bridge unit
  2. Check installed firmware version
    Log into the web interface and navigate to System Settings or About page to view the BSP firmware version; alternatively, check via CLI if available
    Affected if Firmware version is below BSP 6.1.0 or version cannot be determined
  3. Verify web interface is accessible
    Attempt to access the device web interface via HTTPS on the configured IP address
    Affected if Web interface is reachable and accepts authentication
  4. Check Plugin Manager module availability
    After authentication, navigate to the Plugin Manager section in the web interface to confirm the plugin upload functionality exists
    Affected if Plugin Manager is accessible to the authenticated user account
  5. Inspect uploaded plugin files
    Check the plugin storage directory (typically /plugins or similar path) for any Python files that may have been uploaded
    Affected if Any unexpected or suspicious Python files are present in the plugin directory

A Wattsense Bridge device running firmware below BSP 6.1.0 with an accessible web interface and enabled Plugin Manager feature is potentially affected if the device has any uploaded Python plugin 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to BSP >= 6.1.0 and enforce least-privilege access controls on web interface accounts to limit plugin upload capabilities.

Recommended fix High confidence

BSP 6.1.0 or later

  1. Identify the current firmware version of the Wattsense Bridge device by accessing the web interface or checking the device status page
  2. Navigate to the Wattsense support site (support.wattsense.com) and locate the firmware download section for Bridge devices
  3. Download the latest firmware version BSP 6.1.0 or later from the official source
  4. Access the device administration interface and locate the firmware update or system settings section
  5. Upload and install the downloaded firmware file following the on-screen instructions provided by Wattsense
  6. After the upgrade completes, verify the new firmware version is installed correctly
  7. Confirm that the Plugin Manager now properly validates uploaded files and restricts Python file uploads
Caveat Review Wattsense release notes for any configuration or compatibility changes between your current version and 6.1.0 before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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