# CVE-2023-49133: Command injection in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3)

> An unauthenticated attacker can execute arbitrary commands on Tp-Link access points via crafted network requests to the enable_test_mode functionality.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-fqq4-qr43-h5jq

## What is CVE-2023-49133?

CVE-2023-49133 is a high-severity command injection vulnerability in Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3), published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command execution vulnerability exists in the tddpd enable_test_mode functionality of Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) v5.1.0 Build 20220926 and Tp-Link N300 Wireless Access Point (EAP115 V4) v5.0.4 Build 20220216. A specially crafted series of network requests can lead to arbitrary command execution. An attacker can send a sequence of unauthenticated packets to trigger this vulnerability.This vulnerability impacts `uclited` on the EAP225(V3) 5.1.0 Build 20220926 of the AC1350 Wireless MU-MIMO Gigabit Access Point.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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

It affects 2 products.


Products: Tp-Link Eap115 Firmware, Tp-Link Eap225 Firmware.

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

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

## Is CVE-2023-49133 being exploited?

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

## Other vulnerabilities in Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3)

- [CVE-2023-49134](https://insights.sbomify.com/CVE-2023-49134/): Command injection in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 8.1)
- [CVE-2023-49907](https://insights.sbomify.com/CVE-2023-49907/): Memory corruption in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 7.2)
- [CVE-2023-49910](https://insights.sbomify.com/CVE-2023-49910/): Memory corruption in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 7.2)
- [CVE-2023-49911](https://insights.sbomify.com/CVE-2023-49911/): Memory corruption in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 7.2)
- [CVE-2023-49912](https://insights.sbomify.com/CVE-2023-49912/): Memory corruption in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49133 is a high-severity command injection vulnerability in Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3), published on 9 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49133 in the wild and no public exploit code.

Affected product: Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3). 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-49133/ (Markdown: https://insights.sbomify.com/CVE-2023-49133/index.md)
```

## Sources

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

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