CVE-2026-24441
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 · uneditedShenzhen Tenda AC7 firmware version V03.03.03.01_cn and prior expose account credentials in plaintext within HTTP responses, allowing an on-path attacker to obtain sensitive authentication material.
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 confidenceThe Tenda AC7 firmware (V03.03.03.01_cn and prior) returns user account credentials in plaintext within HTTP response bodies. When users authenticate or perform certain actions, the web server includes sensitive authentication material (likely usernames and passwords) directly in the response that an on-path attacker intercepting network traffic can read in cleartext.
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<= 03.03.03.01CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the installed firmware versionAccess the Tenda AC7 web interface (typically at 192.168.0.1) and look for the firmware version in System Settings or Status page. Alternatively, check via telnet/SSH if enabled by running 'cat /proc/version' or checking /etc/version file.Affected if The firmware version is V03.03.03.01_cn or any version <= 03.03.03.01 (including older releases).
-
Confirm the device uses unencrypted HTTPObserve the URL scheme when accessing the router web interface. If it shows http:// rather than https://, or try accessing via HTTP to confirm the device accepts it.Affected if The router web interface is accessible over plain HTTP (port 80) without TLS encryption.
-
Capture and inspect HTTP authentication responsesUse a network capture tool (Wireshark, tcpdump) or a browser developer tool to capture traffic while logging into the router or performing actions. Inspect HTTP response bodies for the presence of username or password fields in cleartext.Affected if HTTP responses contain plaintext credentials (usernames or passwords) in the response body, headers, or cookies.
-
Test for credential exposure in API endpointsUse a tool like Burp Suite or curl to send authenticated requests to common endpoints (e.g., /login, /cgi-bin/, /api/) and examine the full response for any sensitive data leakage.Affected if Any API or CGI endpoint returns user credentials in plaintext within the response.
You are affected if your Tenda AC7 firmware is version 03.03.03.01 or lower AND the device returns user credentials in plaintext within HTTP response bodies during authentication or other actions.
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 dataUpgrade to a patched firmware version if available; otherwise, avoid transmitting sensitive data over unencrypted HTTP and consider network segmentation to limit on-path attack exposure. If the device is compromised, rotate all credentials immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24441 — 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-2026-24441 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