dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-7503

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-11
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
An OEM IP camera manufactured by Shenzhen Liandian Communication Technology LTD exposes a Telnet service (port 23) with undocumented, default credentials. The Telnet service is enabled by default and is not disclosed or configurable via the device’s web interface or user manual. An attacker with network access can authenticate using default credentials and gain root-level shell access to the device. The affected firmware version is AppFHE1_V1.0.6.0 (Kernel: KerFHE1_PTZ_WIFI_V3.1.1, Hardware: HwFHE1_WF6_PTZ_WIFI_20201218). No official fix or firmware update is available, and the vendor could not be contacted. This vulnerability allows for remote code execution and privilege escalation.

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

An OEM IP camera from Shenzhen Liandian Communication Technology exposes an undocumented Telnet service on port 23 with hardcoded default credentials. Attackers with network access can authenticate and obtain root-level shell access, enabling full device compromise and potential remote code execution.

MitigationSince no firmware patch is available, organizations should immediately block Telnet port 23 at network boundaries, isolate affected devices in a restricted network segment, and consider replacing the devices with alternatives from vendors that provide security updates.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Red

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 the device manufacturer
    Access the camera's web interface or check the device label/marketing materials to confirm the manufacturer is Shenzhen Liandian Communication Technology or an OEM derivative.
    Affected if The device is manufactured by Shenzhen Liandian Communication Technology or is an OEM version from this vendor.
  2. Verify Telnet service availability on port 23
    Scan the device's IP address for open port 23 using a network scanner (for example, nmap -p 23 <device_ip>) or check network firewall rules for inbound Telnet access.
    Affected if Port 23/Telnet is exposed and accessible on the device.
  3. Confirm Telnet authentication with default credentials
    Attempt Telnet authentication to the device using the hardcoded default credentials associated with this CVE. Successful login confirms the vulnerability.
    Affected if The hardcoded credentials allow Telnet login and provide root-level shell access.

A user is affected if they have an IP camera from Shenzhen Liandian Communication Technology with port 23/Telnet exposed and accessible using the hardcoded default credentials.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no firmware patch is available, organizations should immediately block Telnet port 23 at network boundaries, isolate affected devices in a restricted network segment, and consider replacing the devices with alternatives from vendors that provide security updates.

Recommended fix High confidence
  1. Isolate the affected device on a restricted network VLAN with no direct internet exposure
  2. Block inbound Telnet (port 23) at network perimeter firewalls or edge devices
  3. If the device supports alternative management protocols, disable Telnet via any available administrative interface even if undocumented
  4. Implement network intrusion detection to monitor for suspicious Telnet authentication attempts
  5. Consider replacing the affected device with an alternative product from a vendor that provides security updates
  6. If continued use is required, monitor vendor communications periodically for future firmware releases addressing this vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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