# CVE-2023-27098: Hardcoded credentials in n/a

> Attackers can access the login panel using hardcoded credentials in the TP-Link Tapo mobile application, potentially leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-5cjr-mrq7-q7wq

## What is CVE-2023-27098?

CVE-2023-27098 is a high-severity vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2023-27098?

It affects 1 product.


Products: Tp-Link Tapo.

## How do I fix CVE-2023-27098?

No fix has been published for CVE-2023-27098 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-27098 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27098 exists.

## Other vulnerabilities in n/a

- [CVE-2023-38907](https://insights.sbomify.com/CVE-2023-38907/): Other in n/a (high 7.5)
- [CVE-2023-34829](https://insights.sbomify.com/CVE-2023-34829/): Information disclosure in n/a (medium 6.5)
- [CVE-2023-38908](https://insights.sbomify.com/CVE-2023-38908/): Information disclosure in n/a (medium 6.5)
- [CVE-2023-38909](https://insights.sbomify.com/CVE-2023-38909/): Weak cryptography in n/a (medium 6.5)
- [CVE-2023-38906](https://insights.sbomify.com/CVE-2023-38906/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27098 and fix it if it is affected.

What it is: CVE-2023-27098 is a high-severity vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27098 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-27098/ (Markdown: https://insights.sbomify.com/CVE-2023-27098/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-27098
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-27098
- OSV: https://osv.dev/vulnerability/CVE-2023-27098

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-27098/
Summaries are generated and may contain mistakes; the official description above is the record.