CVE-2019-13151
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 issue was discovered in TRENDnet TEW-827DRU firmware before 2.05B11. There is a command injection in apply.cgi (exploitable with authentication) via the action set_sta_enrollee_pin_5g and the key wps_sta_enrollee_pin.
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 TRENDnet TEW-827DRU router firmware before 2.05B11 contains a command injection vulnerability in the apply.cgi web interface. An authenticated attacker can inject arbitrary OS commands through the wps_sta_enrollee_pin parameter when using the set_sta_enrollee_pin_5g action, leading to complete device compromise.
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< 2.05b11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 router firmware versionLog into the TRENDnet TEW-827DRU web interface and navigate to the Status or System Information page to view the current firmware version. Alternatively, if you have access to the firmware image file, use binwalk or strings to extract the version string.Affected if The installed firmware version is less than 2.05B11
-
Verify the apply.cgi web interface is accessibleAttempt to access the apply.cgi endpoint by sending an HTTP GET request to http://[router-ip]/apply.cgi. A successful response indicates the web interface is enabled.Affected if The web interface responds and is reachable on the network
-
Confirm WPS functionality is enabledIn the router web interface, navigate to the Wireless settings section and check whether Wi-Fi Protected Setup (WPS) is enabled, particularly for the 5GHz band.Affected if WPS is enabled on the device, which is required for the vulnerable parameter to be processed
-
Check for unauthorized administrative accessReview the router administration logs or active sessions for any unexpected authenticated sessions, and verify that default administrator credentials have not been changed.Affected if The device allows authenticated access (whether through default credentials, weak passwords, or compromised admin sessions), which is necessary to exploit this vulnerability
The device is affected if the firmware version is below 2.05B11, the web interface is accessible, and an attacker can authenticate to submit the malicious wps_sta_enrollee_pin parameter via the set_sta_enrollee_pin_5g action.
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 data2.05b11
Update the router firmware to version 2.05B11 or later from the vendor. If patching is not possible, restrict administrative access to trusted networks and monitor for unauthorized access.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13151 — 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-2019-13151 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