dbcve.org
Sge Plc1000 FirmwareOperating system · Circutor

CVE-2025-11786

CRITICAL · 9.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 →
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
Stack-based buffer overflow vulnerability in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. In the 'SetUserPassword()' function, the 'newPassword' parameter is directly embedded in a shell command string using 'sprintf()' without any sanitisation or validation, and then executed using 'system()'. This allows an attacker to inject arbitrary shell commands that will be executed with the same privileges as the application.

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

Stack-based buffer overflow and command injection in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. The SetUserPassword() function accepts a newPassword parameter that is directly concatenated into a shell command string via sprintf() without any input validation or sanitization, then executed via system(). This allows unauthenticated or authenticated attackers to inject arbitrary OS commands with the application's privileges.

MitigationImplement strict input validation on all user-supplied parameters to reject shell metacharacters, replace system() calls with safer alternatives, and apply vendor firmware updates. Network segmentation and restricting access to the PLC management interface should be applied as compensating controls until the fix is available.

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

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

  1. Identify Circutor SGE-PLC devices on the network
    Scan the network for devices responding to HTTP/HTTPS on ports 80, 8080, 443, or 8443. Identify devices by checking HTTP response headers, favicon, or login pages for 'SGE-PLC1000', 'SGE-PLC50', or 'Circutor' branding.
    Affected if A Circutor SGE-PLC1000 or SGE-PLC50 device is found on the network.
  2. Check the firmware version
    Log into the device web interface and navigate to the System Information, About, or Firmware section. Alternatively, check the HTTP response headers or API endpoints that may expose version information.
    Affected if The firmware version is exactly 9.0.2.
  3. Verify the web management interface is accessible
    Attempt to access the device login page via HTTP/HTTPS. The vulnerable SetUserPassword() function is exposed through the web interface.
    Affected if The web management interface is reachable over the network.
  4. Confirm unauthenticated access to password change function
    Inspect the web application endpoints for the SetUserPassword or password change functionality. Check if the function can be reached without authentication or after authentication.
    Affected if The SetUserPassword() function is accessible without strict authentication requirements.
  5. Assess network exposure of the management interface
    Determine if the device management interface is on a shared network segment or directly accessible from less-trusted networks. Check routing tables and firewall rules.
    Affected if The management interface is accessible from network segments that should not have PLC management access.

A user is affected if they have a Circutor SGE-PLC1000 or SGE-PLC50 device running firmware version 9.0.2 with its web management interface accessible on the network.

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

Implement strict input validation on all user-supplied parameters to reject shell metacharacters, replace system() calls with safer alternatives, and apply vendor firmware updates. Network segmentation and restricting access to the PLC management interface should be applied as compensating controls until the fix is available.

Fix this in Sge Plc1000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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