CVE-2025-11787
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 · uneditedCommand injection vulnerability in the operating system in Circutor SGE-PLC1000/SGE-PLC50 v9.0.2 through the 'GetDNS()', 'CheckPing()' and 'TraceRoute()' functions.
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 confidenceCommand injection vulnerability in Circutor SGE-PLC1000/SGE-PLC50 devices allows remote attackers to execute arbitrary OS commands through the GetDNS(), CheckPing(), and TraceRoute() functions in firmware v9.0.2 through later versions. These network diagnostic functions fail to properly sanitize input, enabling OS command injection.
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= 9.0.2= 9.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device modelIdentify the Circutor device by checking the web interface header, device label, or SNMP/sysinfo output. Look for SGE-PLC1000 or SGE-PLC50 identifiersAffected if Device is not an SGE-PLC1000 or SGE-PLC50 model
-
Retrieve firmware versionAccess the device web interface System Settings or Status page, or query the device API for firmware version information. Compare the version number to 9.0.2Affected if Firmware version is 9.0.2 or later
-
Locate network diagnostic functionsNavigate the device web interface to find the GetDNS, CheckPing, and TraceRoute functions. These are typically under Network Tools, Diagnostics, or System Utilities menusAffected if These functions exist and are accessible in the interface
-
Verify function accessibilityDetermine if these functions can be invoked via HTTP requests without authentication, or check if they are exposed to unauthenticated or untrusted network segmentsAffected if The functions are reachable without proper authentication or from untrusted networks
-
Assess network exposureReview firewall rules, access control lists, and network segmentation to determine if the device management interface is directly accessible from the internet or untrusted VLANsAffected if Device is exposed to untrusted networks without firewall protection
Environment is affected if running a Circutor SGE-PLC1000 or SGE-PLC50 with firmware >=9.0.2 and the GetDNS/CheckPing/TraceRoute functions are network-accessible
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware patch when available; if no patch exists, isolate affected devices on a dedicated network segment and restrict access to these functions via firewall rules or access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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