dbcve.org
Sge Plc1000 FirmwareOperating system · Circutor

CVE-2025-11789

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Out-of-bounds read vulnerability in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. The 'DownloadFile' function converts a parameter to an integer using 'atoi()' and then uses it as an index in the 'FilesDownload' array with '(&FilesDownload)[iVar2]'. If the parameter is too large, it will access memory beyond the limits.

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

Out-of-bounds read vulnerability in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2. The DownloadFile function uses atoi() to convert an input parameter to an integer without validating its value, then uses this integer as an index into the FilesDownload array. When the parameter value exceeds the array bounds, memory is accessed beyond the allocated buffer, potentially allowing disclosure of sensitive information.

MitigationImplement strict bounds checking on the converted integer value before array access, ensuring the index falls within the valid range of the FilesDownload array. Consider using safer alternatives to atoi() that provide error handling.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 web interface or use SNMP to query the device for its model (SGE-PLC1000 or SGE-PLC50) and firmware version information. Check the 'About' or 'System Information' page for the exact firmware build number.
    Affected if The firmware version is exactly 9.0.2 on a SGE-PLC1000 or SGE-PLC50 device.
  2. Confirm remote management interface is enabled
    Check if the device web server or remote management interface is accessible and enabled on the network. This is typically found in the device network settings or security configuration.
    Affected if The web interface or remote management is exposed and accessible.
  3. Verify DownloadFile function accessibility
    Locate the DownloadFile function endpoint or interface. In the web application, this may appear as a file download feature, potentially under sections like 'File Management', 'Data Export', or similar. Check if this functionality is present and accessible.
    Affected if The DownloadFile function is exposed and accepts user-supplied parameters.
  4. Test for out-of-bounds array access
    If the DownloadFile function accepts a numeric parameter, send requests with values exceeding typical array bounds (e.g., very large numbers or negative values) to observe if unexpected data is returned or if the application behaves unexpectedly. This is a passive observation only, do not attempt exploitation.
    Affected if The device processes requests to DownloadFile with arbitrary integer parameters without bounds validation, potentially exposing memory contents.

The environment is affected if running Circutor SGE-PLC1000 or SGE-PLC50 with firmware version exactly 9.0.2 and the DownloadFile function is accessible via the web interface or remote management.

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 bounds checking on the converted integer value before array access, ensuring the index falls within the valid range of the FilesDownload array. Consider using safer alternatives to atoi() that provide error handling.

Fix this in Sge Plc1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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