Categories
CVE-2023-27098 high CVSS 7.5

Vulnerability in TP-Link Tapo APK (CVE-2023-27098)

Summary

Vulnerability in TP-Link Tapo APK (CVE-2023-27098). Confidential information can be exposed externally.

Original description

The description as published by the source.

TP-Link Tapo APK up to v2.12.703 uses hardcoded credentials for access to the login panel.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2023-27098 was discovered in TP-Link Tapo APK.
Severity is High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "TP-Link Tapo APK CVE-2023-27098".

CVE-2023-27098 (TP-Link Tapo APK). Severity: High / CVSSv3 7.5. Category: CWE-312.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2023-27098) in TP-Link Tapo APK. A serious software flaw has been identified.

📍 Affected scope

Target versions of TP-Link Tapo APK (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: High (CVSS 7.5/10). If exploited, attackers can leak data or disrupt key functionality.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-312)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details