CVE-2025-1819
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 vulnerability, which was classified as critical, was found in Tenda AC7 1200M 15.03.06.44. Affected is the function TendaTelnet of the file /goform/telnet. The manipulation of the argument lan_ip leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
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 confidenceOS command injection vulnerability in Tenda AC7 1200M router firmware 15.03.06.44 allows remote attackers to execute arbitrary operating system commands via the unsanitized 'lan_ip' parameter in the /goform/telnet endpoint's TendaTelnet function.
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= 15.03.06.44CVSS 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.
-
Confirm router model and firmware versionAccess the router's web admin interface (typically 192.168.0.1) and navigate to System Settings > Firmware Version, or check the device label. Alternatively, use Nmap or curl to probe the device and examine HTTP responses for version strings.Affected if Firmware version is exactly 15.03.06.44
-
Verify telnet service is reachableRun 'telnet <router_ip>' on the router's LAN IP (commonly 192.168.0.1) or use 'nmap -p 23 <router_ip>' to check if port 23 is open.Affected if Telnet port 23 is open and responds to connection attempts
-
Test /goform/telnet endpoint accessibilitySend an HTTP POST request to http://<router_ip>/goform/telnet using curl or Burp Suite. Observe if the endpoint responds or accepts parameters.Affected if The /goform/telnet endpoint is reachable and does not require authentication or is accessible from the network
-
Check if lan_ip parameter is acceptedSend a crafted POST request to /goform/telnet with a test value in the 'lan_ip' parameter (e.g., lan_ip=test). Monitor the response for command injection behavior or errors indicating the parameter is processed.Affected if The router accepts and processes the lan_ip parameter without sanitization checks in the response
A user is affected if they are running Tenda AC7 firmware version 15.03.06.44 AND the telnet functionality is enabled/accessible on the network, allowing the vulnerable /goform/telnet endpoint to be reached.
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 firmware patch when available; if no update exists, disable the telnet functionality and isolate the device behind a restrictive firewall to prevent remote exploitation.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1819 — 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-1819 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