# CVE-2023-32619: Hardcoded credentials in Archer C50

> Hard-coded credentials in TP-Link Archer C50 and C55 routers allow network-adjacent attackers to execute arbitrary OS commands.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-348j-ghgq-g3hj

## What is CVE-2023-32619?

CVE-2023-32619 is a high-severity vulnerability in TP-LINK Archer C50, published on 6 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Archer C50 firmware versions prior to 'Archer C50(JP)_V3_230505' and Archer C55 firmware versions prior to 'Archer C55(JP)_V1_230506' use hard-coded credentials to login to the affected device, which may allow a network-adjacent unauthenticated attacker to execute an arbitrary OS command.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


Products: Tp-Link Archer C50 V3 Firmware, Tp-Link Archer C55 Firmware.

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

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

## Is CVE-2023-32619 being exploited?

There is no known exploitation of CVE-2023-32619 in the wild and no public exploit code.

## Other vulnerabilities in TP-LINK Archer C50

- [CVE-2023-31188](https://insights.sbomify.com/CVE-2023-31188/): Command injection in Archer C20 (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32619 is a high-severity vulnerability in TP-LINK Archer C50, published on 6 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32619 in the wild and no public exploit code.

Affected product: TP-LINK Archer C50. 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-32619/ (Markdown: https://insights.sbomify.com/CVE-2023-32619/index.md)
```

## Sources

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

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