A password-disclosure issue in the web interface on certain TP-Link devices allows a remote attacker to get full administrative access to th
Noroxi assessment
Priority: Plan (action score 41/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.6% (FIRST EPSS); higher than 94.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
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
A password-disclosure issue in the web interface on certain TP-Link devices allows a remote attacker to get full administrative access to the web panel. This affects WA901ND devices before 3.16.9(201211) beta, and Archer C5, Archer C7, MR3420, MR6400, WA701ND, WA801ND, WDR3500, WDR3600, WE843N, WR1043ND, WR1045ND, WR740N, WR741ND, WR749N, WR802N, WR840N, WR841HP, WR841N, WR842N, WR842ND, WR845N, WR940N, WR941HP, WR945N, WR949N, and WRD4300 devices.
- Published
- Dec 25, 2020
- Updated
- Jun 16, 2026
- EPSS
- 7.6% · 94th percentile
- CWE
- —
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | wa901nd firmware | cpe:2.3:o:tp-link:wa901nd_firmware |
| tp-link | wa901nd | cpe:2.3:h:tp-link:wa901nd |
| tp-link | archer c5 firmware | cpe:2.3:o:tp-link:archer_c5_firmware |
| tp-link | archer c5 | cpe:2.3:h:tp-link:archer_c5 |
| tp-link | archer c7 firmware | cpe:2.3:o:tp-link:archer_c7_firmware |
| tp-link | archer c7 | cpe:2.3:h:tp-link:archer_c7 |
| tp-link | mr3420 firmware | cpe:2.3:o:tp-link:mr3420_firmware |
| tp-link | mr3420 | cpe:2.3:h:tp-link:mr3420 |
| tp-link | mr6400 firmware | cpe:2.3:o:tp-link:mr6400_firmware |
| tp-link | mr6400 | cpe:2.3:h:tp-link:mr6400 |
| tp-link | wa701nd firmware | cpe:2.3:o:tp-link:wa701nd_firmware |
| tp-link | wa701nd | cpe:2.3:h:tp-link:wa701nd |
and 42 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tp-link archer c5 firmwareall versions
- tp-link archer c7 firmwareall versions
- tp-link mr3420 firmwareall versions
- tp-link mr6400 firmwareall versions
- tp-link wa701nd firmwareall versions
- tp-link wa801nd firmwareall versions
- tp-link wa901nd firmwarebefore 3.16.9\(201211\)_beta
- tp-link wdr3500 firmwareall versions
- tp-link wdr3600 firmwareall versions
- tp-link we843n firmwareall versions
- tp-link wr1043nd firmwareall versions
- tp-link wr1045nd firmwareall versions
- tp-link wr740n firmwareall versions
- tp-link wr741nd firmwareall versions
- tp-link wr749n firmwareall versions
- tp-link wr802n firmwareall versions
- tp-link wr840n firmwareall versions
- tp-link wr841hp firmwareall versions
- tp-link wr841n firmwareall versions
- tp-link wr842n firmwareall versions
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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×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 |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:3 | 2024-10-18 |
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.
- Published
- First PoC+1392 d
- TodayOct 23, 2026+2128 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.