dbcve.org
Sge Plc1000 FirmwareOperating system · Circutor

CVE-2025-11781

HIGH · 7.8 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Use of hardcoded cryptographic keys in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. The affected firmware contains a hardcoded static authentication key. An attacker with local access to the device can extract this key (e.g., by analysing the firmware image or memory dump) and create valid firmware update packages. This bypasses all intended access controls and grants full administrative privileges.

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

The Circutor SGE-PLC1000/SGE-PLC50 v9.0.2 firmware contains a hardcoded static authentication key embedded in the firmware image. An attacker with local access can extract this key through firmware analysis or memory dumping, allowing them to craft valid firmware update packages that bypass all access controls and grant full administrative privileges.

MitigationReplace the hardcoded key with a secure key management solution (e.g., hardware security module, secure key storage, or per-device unique keys), regenerate all credentials, issue firmware updates with proper cryptographic key generation, and rotate any exposed credentials.

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
Sge Plc1000 FirmwareOperating system
Affected:= 9.0.2
Sge Plc50 FirmwareOperating system
Affected:= 9.0.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify device model and firmware version
    Access the device's web interface, console, or administrative panel and locate the firmware version information. For SGE-PLC devices, check System Information or About pages in the web UI, or use CLI commands like 'show version' if available.
    Affected if The device is a Circutor SGE-PLC1000 or SGE-PLC50 running firmware version exactly 9.0.2
  2. Check firmware update capability exposure
    Locate the firmware update or upgrade functionality in the device's web interface (typically under Administration, Maintenance, or Firmware sections). Determine if this feature is accessible and whether it requires authentication.
    Affected if Firmware update interface is accessible and accepts packages without requiring strong multi-factor authentication or per-device unique credentials
  3. Assess network exposure of management interfaces
    Scan the network for open ports commonly used for device management such as HTTP (80), HTTPS (443), Telnet (23), SSH (22), or FTP (21). Verify if these interfaces are exposed to untrusted networks.
    Affected if Management interfaces including firmware update functionality are exposed to the internet or untrusted network segments
  4. Verify firmware integrity controls
    If you have access to firmware images, examine whether the firmware update mechanism includes cryptographic signature verification. Check if the device rejects unsigned or invalidly signed firmware packages.
    Affected if Firmware updates can be applied without valid cryptographic signatures or the device lacks signature verification entirely

You are affected if you operate a Circutor SGE-PLC1000 or SGE-PLC50 device on firmware version 9.0.2 with firmware update functionality accessible without strong per-device authentication and signature verification.

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

Replace the hardcoded key with a secure key management solution (e.g., hardware security module, secure key storage, or per-device unique keys), regenerate all credentials, issue firmware updates with proper cryptographic key generation, and rotate any exposed credentials.

Fix this in Sge Plc1000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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