# CVE-2023-49913: Memory corruption in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3)

> An authenticated attacker can achieve remote code execution via a stack-based buffer overflow in the web interface of Tp-Link access points.

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

## What is CVE-2023-49913?

CVE-2023-49913 is a high-severity memory corruption vulnerability in Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3), published on 9 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A stack-based buffer overflow vulnerability exists in the web interface Radio Scheduling functionality of Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) v5.1.0 Build 20220926. A specially crafted series of HTTP requests can lead to remote code execution. An attacker can make an authenticated HTTP request to trigger this vulnerability.This vulnerability refers specifically to the overflow that occurs via the `action` parameter at offset `0x422448` of the `httpd` binary shipped with v5.0.4 Build 20220216 of the EAP115.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 2 products.


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

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

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

## Is CVE-2023-49913 being exploited?

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

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

- [CVE-2023-49133](https://insights.sbomify.com/CVE-2023-49133/): Command injection in AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3) (high 8.1)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49913 is a high-severity memory corruption vulnerability in Tp-Link AC1350 Wireless MU-MIMO Gigabit Access Point (EAP225 V3), published on 9 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49913 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-49913/ (Markdown: https://insights.sbomify.com/CVE-2023-49913/index.md)
```

## Sources

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

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