CVE-2025-27129
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 · uneditedAn authentication bypass vulnerability exists in the HTTP authentication functionality of Tenda AC6 V5.0 V02.03.01.110. A specially crafted HTTP request can lead to arbitrary code execution. An attacker can send packets to trigger this vulnerability.
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 · moderate confidenceTenda AC6 V5.0 firmware V02.03.01.110 contains an authentication bypass vulnerability in its HTTP authentication mechanism. By sending specially crafted HTTP requests, an unauthenticated attacker can bypass authentication checks and achieve arbitrary code execution on the affected device.
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= 02.03.01.110CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify firmware versionAccess the router web interface and navigate to System Settings or Administration section to view firmware version, or check the version string in the router's web UI footerAffected if Firmware version is exactly 02.03.01.110
-
Confirm HTTP management interface is enabledIn router settings, locate the remote management or HTTP access configuration (typically under Advanced Settings, System Tools, or Administration > Remote Management)Affected if HTTP management interface is enabled and accessible from network
-
Check remote access configurationInspect the router's remote access settings to determine if HTTP management is allowed from WAN/remote sources versus LAN-onlyAffected if Remote HTTP management is permitted from external network sources
-
Verify HTTP service is listeningFrom a system on the same network, use a browser to access the router's HTTP interface at its LAN IP address (commonly 192.168.0.1 or 192.168.1.1)Affected if Router HTTP web interface is responsive and accepts authentication requests
-
Assess network exposureCheck router firewall or access control settings to determine if HTTP port (80) is forwarded or exposed to WANAffected if HTTP service is exposed to untrusted network segments or the internet
Environment is affected if Tenda AC6 firmware version is exactly 02.03.01.110 and the HTTP management interface is enabled and accessible
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.
From vendor dataApply vendor-supplied firmware patch if available; otherwise, disable remote HTTP administration, implement network segmentation, and restrict access to the device management interface to trusted IP addresses or VPN tunnels.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27129 — 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-27129 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