Trendnet AC2600 TEW-827DRU version 2.08B01 does not properly implement csrf protections.

published 2021-12-30 4y ago modified 2026-06-17 4mo ago also EUVD-2021-7622

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 51%
public exploits: 0; none known

Trendnet AC2600 TEW-827DRU version 2.08B01 does not properly implement csrf protections. Most pages lack proper usage of CSRF protections or mitigations. Additionally, pages that do make use of CSRF tokens are trivially bypassable as the server does not appear to validate them properly (i.e. re-using an old token or finding the token thru some other method is possible).

Is CVE-2021-20165 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

tenable.com https://www.tenable.com/security/research/tra-2021-54 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

n/a Trendnet AC2600 TEW-827DRU

Classification

Weakness

CWE-352 Cross-Site Request Forgery

References

tenable.com /security/research/tra-2021-54
exploit, third-party-advisory

Sources

CVE List CVE-2021-20165
NVD CVE-2021-20165

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.