CVE-2024-48459
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 command execution vulnerability exists in the AX2 Pro home router produced by Shenzhen Tenda Technology Co., Ltd. (Jixiang Tenda) v.DI_7003G-19.12.24A1V16.03.29.50;V16.03.29.50;V16.03.29.50. An attacker can exploit this vulnerability by constructing a malicious payload to execute commands and further obtain shell access to the router's file system with the highest privileges.
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 confidenceA command injection vulnerability in the Tenda AX2 Pro home router (firmware DI_7003G-19.12.24A1V16.03.29.50) allows remote attackers to execute arbitrary commands with highest privileges by sending a malicious payload, achieving full shell access to the router's filesystem.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm device model is Tenda AX2 ProAccess the router web interface or check the device label. Common login URL is http://192.168.0.1. Navigate to System Settings or Device Info to verify the model name displays as 'AX2 Pro' or similar.Affected if The device is not a Tenda AX2 Pro router, then this specific CVE does not apply.
-
Check installed firmware versionIn the router web interface, go to System Settings > Firmware Upgrade or Device Info. Look for a version string such as 'V16.03.29.50' or the full build string 'DI_7003G-19.12.24A1V16.03.29.50'. Alternatively, check the firmware file if you have access to it.Affected if The installed firmware version matches exactly 'DI_7003G-19.12.24A1V16.03.29.50' or falls within the version range ending at this build, indicating the vulnerable code is present.
-
Verify HTTP management interface is accessible from networkAttempt to access the router web interface from an external IP address, or check port forwarding/firewall rules on the router that expose the HTTP service (port 80 or 443) to the WAN interface. Log into the router and inspect Security > Access Control or similar settings.Affected if The router management web interface is reachable from outside the local network, meaning an attacker on the internet could send the malicious payload.
-
Inspect for signs of unauthorized accessCheck the router system logs for unexpected commands, shell sessions, or unfamiliar processes. Look for any new user accounts, modified startup scripts, or unfamiliar files in /tmp or /var directories if you have shell access.Affected if Logs or filesystem show evidence of arbitrary command execution, reverse shells, or unexpected processes that did not originate from legitimate administrator actions.
A user is affected if they are running the Tenda AX2 Pro router with firmware version DI_7003G-19.12.24A1V16.03.29.50 and the router management interface is exposed to the network.
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; if no update exists, replace the device and restrict network access to router management interfaces.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48459 — 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-2024-48459 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