CVE-2025-9971
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 a Missing Authentication vulnerability, allowing unauthenticated remote attackers to manipulate the device via a specific functionality.
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 confidenceMissing authentication in Planet Technology Industrial Cellular Gateway devices allows unauthenticated remote attackers to manipulate the device through a specific functionality. This critical vulnerability (CVSS 9.8) enables full device compromise without credentials, likely through an unprotected network service or API endpoint.
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 web interface or check the device label/console for the exact model name. Confirm it is a Planet Technology Industrial Cellular Gateway series device.Affected if The device is a Planet Technology Industrial Cellular Gateway model.
-
Determine the firmware versionLog into the device management interface (web GUI or CLI) and navigate to the System Information or Firmware version section. Record the installed firmware version number.Affected if The installed firmware version is older than the patched version provided by Planet Technology (compare against vendor release notes when available).
-
Check for exposed management servicesPerform a network port scan (e.g., using nmap) against the device IP address. Identify open ports associated with management interfaces such as HTTP (80/443), SSH (22), Telnet (23), or custom API ports.Affected if Management ports (HTTP, HTTPS, SSH, Telnet, or custom API endpoints) are accessible from untrusted networks without firewall filtering.
-
Test for unauthenticated API accessSend HTTP/HTTPS requests directly to common API endpoints on the device (e.g., /api/, /cgi-bin/, or vendor-specific endpoints) without providing any authentication credentials. Observe if the device returns valid data or allows operations.Affected if The device responds to API requests or allows device manipulation without requiring any authentication credentials.
-
Review network exposureCheck firewall rules, NAT configurations, or ACLs that govern access to the device management interface. Determine if the device is reachable from the internet or untrusted network segments.Affected if The device management interface is directly accessible from the internet or from untrusted network segments without proper access controls.
A user is affected if they operate a Planet Technology Industrial Cellular Gateway device with firmware lacking the authentication fix, especially if the management interface is exposed to untrusted networks.
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 updates when available; immediately restrict network exposure using firewall rules or network segmentation to limit access to the device management interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9971 — 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-9971 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