dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-29270

CRITICAL · 10.0 CVSS v3.1 Published 2025-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows attackers to gain access to the admin panel and complete control of the device.

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

Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics DSE855 (v1.1.0 to v1.1.26) allows unauthenticated attackers to bypass authentication and gain administrative access to the device, achieving full control of the generator controller.

MitigationUpgrade DSE855 firmware to a version beyond v1.1.26 and restrict network exposure of administrative interfaces.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify the device model
    Access the device web interface or check the device label/documentation to confirm it is a Deep Sea Electronics DSE855 generator controller
    Affected if The device is not a DSE855 (different models may have different version schemes)
  2. Determine the firmware version
    Locate the firmware version in the device web interface (typically under System Info, About, or Status page) or via SNMP/syslog if available
    Affected if The installed firmware version falls within the range v1.1.0 through v1.1.26 inclusive
  3. Check network exposure of administrative interface
    Verify if the device web interface (port 80/443 or custom HTTP ports) is exposed to untrusted networks or the public internet
    Affected if The administrative web interface is reachable from untrusted networks without firewall protection
  4. Test realtime.cgi authentication behavior
    Attempt to access the realtime.cgi endpoint directly via HTTP/HTTPS without providing credentials (e.g., http://[device-ip]/cgi-bin/realtime.cgi)
    Affected if The endpoint returns administrative data or allows actions without requiring login credentials

A user is affected if they have a DSE855 device running firmware v1.1.0 through v1.1.26 with the web interface exposed to untrusted networks, and the realtime.cgi endpoint permits unauthenticated access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DSE855 firmware to a version beyond v1.1.26 and restrict network exposure of administrative interfaces.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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