CVE-2025-9972
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 · uneditedCertain models of Industrial Cellular Gateway developed by Planet Technology have an OS Command Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary OS commands and execute them on 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 · moderate confidenceOS command injection vulnerability in Planet Technology Industrial Cellular Gateway devices allows unauthenticated remote attackers to inject and execute arbitrary OS commands. The critical severity (CVSS 9.8) combined with no authentication requirement makes this immediately exploitable and highly dangerous.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web interface or console and locate the device information page to confirm it is a Planet Technology Industrial Cellular Gateway model. Check the device label or management interface for the exact model number.Affected if The device is any Planet Technology Industrial Cellular Gateway model.
-
Locate the firmware versionIn the device's web management interface, navigate to System or Status sections to find the installed firmware version. Record this version number for comparison.Affected if A firmware version is displayed and matches the affected product line.
-
Check if remote management is enabledIn the web interface, go to Network or Administration settings and look for remote management, WAN access, or HTTP/HTTPS management options that allow access from external networks.Affected if Remote management interfaces are enabled and accessible from WAN/untrusted networks.
-
Verify network exposureCheck firewall rules or network configuration to determine if the device's management port (typically HTTP port 80 or HTTPS port 443) is exposed to the internet or untrusted networks.Affected if The device management interface is reachable from external IP addresses or untrusted networks.
-
Inspect for unauthorized access indicatorsReview system logs, access logs, or security event logs for suspicious commands, unexpected IP addresses, or signs of command injection attempts.Affected if Log entries show suspicious commands, unusual IP access, or evidence of command injection activity.
You are affected if you are running any Planet Technology Industrial Cellular Gateway with remote management enabled and exposed to untrusted networks, regardless of firmware version.
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-supplied firmware patches when available; if no patch exists, isolate affected devices behind a firewall or consider device replacement. Disable remote management interfaces from untrusted networks until remediation is complete.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9972 — 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-9972 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