CVE-2025-7375
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA denial-of-service (DoS) vulnerability was identified in Omada EAP610 v3. An attacker with adjacent network access can send crafted requests to cause the device’s HTTP service to crash. This results in temporary service unavailability until the device is rebooted. This issue affects Omada EAP610 firmware versions prior to 1.6.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial-of-service vulnerability exists in the HTTP service of TP-Link Omada EAP610 v3 wireless access points. An attacker with adjacent network access can send specially crafted HTTP requests that cause the service to crash, rendering the device unavailable until manually rebooted. The vulnerability affects firmware versions prior to 1.6.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is EAP610Log into the Omada controller or access the device's web management interface and verify the model number displayed in the device status or information page is exactly 'EAP610'.Affected if The device model is not EAP610 (different models may have different vulnerability status).
-
Check installed firmware versionIn the Omada controller, navigate to the device list or device details page and locate the firmware version field. Alternatively, access the device's web UI and check the firmware version in the system status or information section.Affected if The firmware version shown is less than 1.6.0 (for example, 1.5.x, 1.4.x, etc.).
-
Verify HTTP management service is enabledIn the device settings or management interface, check whether the HTTP (port 80) or HTTPS (port 443) management service is enabled. This is typically found under Access Control, Management, or Security settings in the Omada controller or device web UI.Affected if HTTP management service is enabled and accessible (the vulnerability exploits the HTTP service, so if HTTP is disabled, the attack surface may be reduced).
-
Assess network accessibility of management interfaceDetermine if the management interface is reachable from adjacent network segments. Check VLAN configuration, ACLs, or firewall rules that control access to the device's IP address on ports 80/443. Verify whether the device is on an isolated management VLAN or accessible from user network segments.Affected if The device's HTTP management interface is reachable from network segments accessible to adjacent attackers (the vulnerability requires adjacent network access).
You are affected if the device is an EAP610 running firmware version prior to 1.6.0, the HTTP management service is enabled, and the interface is accessible from an adjacent network segment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.6.0
Upgrade the Omada EAP610 firmware to version 1.6.0 or later to resolve the vulnerability. As a secondary measure, restrict adjacent network access to the management interface using network segmentation or ACLs.
Firmware version 1.6.0
- 1. Download the firmware version 1.6.0 or later from the official TP-Link Omada support portal at support.omadanetworks.com
- 2. Access the Omada EAP610 device through the Omada Controller or web management interface
- 3. Navigate to the firmware upgrade section for the affected EAP610 device
- 4. Upload and apply the firmware version 1.6.0
- 5. After the upgrade completes, verify the device is functioning normally
- 6. Confirm the new firmware version is 1.6.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data