CVE-2020-12109: Certain TP-Link devices allow Command Injection.
Noroxi assessment
Priority: Plan (action score 57/100)
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 74.3% (FIRST EPSS); higher than 99.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Certain TP-Link devices allow Command Injection. This affects NC200 2.1.9 build 200225, NC210 1.0.9 build 200304, NC220 1.3.0 build 200304, NC230 1.3.0 build 200304, NC250 1.3.0 build 200304, NC260 1.5.2 build 200304, and NC450 1.5.3 build 200304.
- Published
- May 4, 2020
- Updated
- Jun 16, 2026
- EPSS
- 74.3% · 99th percentile
- CWE
- CWE-78
Report tools
Action score
57
Add it to your regular patch cycle.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 22 / 30 · 74.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tp-link | nc200 firmware | cpe:2.3:o:tp-link:nc200_firmware |
| tp-link | nc200 | cpe:2.3:h:tp-link:nc200 |
| tp-link | nc210 firmware | cpe:2.3:o:tp-link:nc210_firmware |
| tp-link | nc210 | cpe:2.3:h:tp-link:nc210 |
| tp-link | nc220 firmware | cpe:2.3:o:tp-link:nc220_firmware |
| tp-link | nc220 | cpe:2.3:h:tp-link:nc220 |
| tp-link | nc230 firmware | cpe:2.3:o:tp-link:nc230_firmware |
| tp-link | nc230 | cpe:2.3:h:tp-link:nc230 |
| tp-link | nc250 firmware | cpe:2.3:o:tp-link:nc250_firmware |
| tp-link | nc250 | cpe:2.3:h:tp-link:nc250 |
| tp-link | nc260 firmware | cpe:2.3:o:tp-link:nc260_firmware |
| tp-link | nc260 | cpe:2.3:h:tp-link:nc260 |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link nc200 firmware2.1.6
- tp-link nc200 firmware2.1.9
- tp-link nc210 firmware1.0.3
- tp-link nc210 firmware1.0.4
- tp-link nc210 firmware1.0.9
- tp-link nc220 firmware1.2.0
- tp-link nc220 firmware1.3.0
- tp-link nc230 firmware1.0.3
+12 more rows
- tp-link nc230 firmware1.2.1
- tp-link nc230 firmware1.3.0
- tp-link nc250 firmware1.0.10
- tp-link nc250 firmware1.0.8
- tp-link nc250 firmware1.2.1
- tp-link nc250 firmware1.3.0
- tp-link nc260 firmware1.0.5
- tp-link nc260 firmware1.0.6
- tp-link nc260 firmware1.4.1
- tp-link nc260 firmware1.5.0
- tp-link nc260 firmware1.5.2
- tp-link nc450 firmware1.0.15
Same product
tp-link: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12110Certain TP-Link devices have a Hardcoded Encryption Key.43Plan
- CVE-2020-13224TP-LINK NC200 devices through 2.1.10 build 200401, NC210 devices through 1.0.10 build 200401, NC220 devices through 1.3.1 build 200401…36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Metasploit module | exploit/linux/http/tp_link_ncxxx_bonjour_command_injectionTP-Link Cloud Cameras NCXXX Bonjour Command Injectionexploit | 2020-04-29 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-6 d
- Published
- TodayNov 16, 2026+2387 d
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-768 · Sep 21, 2020(TP Link Kamera Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.