dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-10991

HIGH · 7.0 CVSS v4.0 Published 2025-09-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
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
The attacker may obtain root access by connecting to the UART port and this vulnerability requires the attacker to have the physical access to the device. This issue affects Tapo D230S1 V1.20: before 1.2.2 Build 20250907.

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

The Tapo D230S1 V1.20 security camera has a vulnerability where an attacker with physical access to the device can obtain root privileges by connecting to the UART debug port. This appears to be due to the UART interface providing unauthenticated root shell access or having easily guessable/default credentials in the firmware.

MitigationUpdate the device firmware to version 1.2.2 Build 20250907 or later to remediate this vulnerability. Additionally, restrict physical access to the device and consider disabling or securing the UART interface in production deployments.

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
Physical
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:X

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. Confirm device model
    Locate the physical device or check device documentation/inventory to verify the exact model is Tapo D230S1
    Affected if The device model is Tapo D230S1 and it has not been migrated to a different model series
  2. Check firmware version
    Access the Tapo app or camera web interface to view the firmware version under device settings; alternatively, check the device label or packaging for the firmware build number
    Affected if The firmware version is 1.20 or earlier (specifically V1.20 as listed in the affected versions)
  3. Assess physical security of the device
    Inspect the physical location where the camera is installed; determine if unauthorized individuals could gain physical access to the device housing
    Affected if The camera is installed in an area accessible to untrusted persons, such as public spaces, unlocked rooms, or areas without surveillance
  4. Inspect UART debug port accessibility
    If physically accessible, remove the device housing and examine the circuit board for exposed UART pins (typically 4 pins in a row: TX, RX, GND, VCC); check if the UART interface is externally accessible via a header or connector
    Affected if The UART debug pins are exposed, easily accessible, or connected to an external debug port without physical protection

The device is affected if it is a Tapo D230S1 running firmware version 1.20 and the UART debug interface is physically accessible to untrusted individuals, allowing unauthenticated root shell access.

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

Update the device firmware to version 1.2.2 Build 20250907 or later to remediate this vulnerability. Additionally, restrict physical access to the device and consider disabling or securing the UART interface in production deployments.

Recommended fix Moderate confidence

1.2.2 Build 20250907

  1. Identify the Tapo D230S1 device and confirm it is running firmware version before 1.2.2 Build 20250907
  2. Navigate to TP-Link's official support website (www.tp-link.com) and locate the firmware download section for the Tapo D230S1 model
  3. Download the fixed firmware version 1.2.2 Build 20250907
  4. Access the Tapo app or web management interface for the device
  5. Locate the firmware upgrade option in the device settings
  6. Upload and apply the downloaded firmware file
  7. After the upgrade completes, verify the device is now running firmware version 1.2.2 Build 20250907 or later
  8. As a compensating control, physically secure the device to prevent unauthorized access to the UART port

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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