CVE-2026-15427
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 OS command injection vulnerability exists in the TR-069 / CWMP management interface of Archer VX1800v v1 due to insufficient input validation and sanitization of parameters, allowing crafted input to be executed as system-level commands. Exploitation requires specific conditions such as TR-069 being enabled and ability to influence ACS-delivered commands, compromise or control an ACS server. Successful exploitation may allow arbitrary command execution with root privileges, resulting in complete compromise of the device.
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 confidenceOS command injection vulnerability in the TR-069/CWMP management interface of TP-Link Archer VX1800v v1 allows attackers to execute arbitrary system commands with root privileges due to insufficient input validation and sanitization of parameters passed to the CWMP interface.
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< 0.16.0= 2.0.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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 the device model and firmware versionAccess the router's web administration interface and navigate to the Status or System Information page to view the hardware model and firmware version. Alternatively, use the command line (e.g., 'cat /proc/version' or '固件版本' in the web UI) to retrieve version details.Affected if The device is a TP-Link Archer VX1800v v1 running any firmware version within the affected range (verify against vendor advisory).
-
Verify TR-069/CWMP is enabledIn the router's web UI, locate the TR-069 or CWMP settings (usually under Advanced > Administration > TR-069 or similar). Check if the 'Enable TR-069' or 'Enable CWMP' option is checked/active.Affected if TR-069/CWMP management interface is currently enabled on the device.
-
Inspect the ACS server configurationIn the same TR-069/CWMP settings page, note the configured ACS URL (ACS Server URL). Verify whether the ACS server is under your administrative control and located on a trusted network segment.Affected if The ACS URL points to an untrusted or externally accessible server, or the ACS server itself is not secured.
-
Check for unauthorized ACS server changesReview logs or network traffic for any unexpected changes to the ACS server URL or unusual CWMP/TR-069 traffic patterns that may indicate compromise of the ACS server.Affected if The ACS server URL has been altered without authorization or suspicious CWMP traffic is detected.
You are affected if you are using a TP-Link Archer VX1800v v1 router with TR-069/CWMP enabled and the ACS server is either compromised, externally accessible, or not fully trusted and secured.
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 data0.16.0
Disable TR-069/CWMP if not required, implement network segmentation to restrict ACS server access, and monitor for unauthorized ACS server connections or unexpected command submissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15427 — 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-15427 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