Tew 831dr FirmwareOperating system · Trendnet

CVE-2022-30326

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
An issue was found on TRENDnet TEW-831DR 1.0 601.130.1.1356 devices. The network pre-shared key field on the web interface is vulnerable to XSS. An attacker can use a simple XSS payload to crash the basic.config page of the web interface.

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 confidence

Cross-site scripting (XSS) vulnerability in the network pre-shared key input field on the TRENDnet TEW-831DR router web interface. User-supplied input in the PSK field is not properly sanitized, allowing injection of malicious script that crashes the basic.config page.

MitigationImplement input validation and output encoding on the pre-shared key field to neutralize XSS payloads; validate and sanitize all user-supplied data before rendering. Check vendor for firmware updates.

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
Tew 831dr FirmwareOperating system
Affected:= 1.0_601.130.1.1356

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm router model
    Access the router web interface or check the device label to verify the model is TRENDnet TEW-831DR
    Affected if Device is not a TRENDnet TEW-831DR router
  2. Check firmware version
    Log into the router admin panel and navigate to the system or status page to view the firmware version; compare to 1.0_601.130.1.1356
    Affected if Firmware version is 1.0_601.130.1.1356
  3. Access the basic.config page
    Navigate to http://<router_ip>/basic.config in a web browser while authenticated to the router
    Affected if The basic.config page loads successfully
  4. Locate the PSK input field
    On the basic.config page, find the wireless security or pre-shared key (PSK) input field where wireless passwords are configured
    Affected if The PSK field is present and accepts user input

All four conditions must be true: you must have a TRENDnet TEW-831DR router running firmware version 1.0_601.130.1.1356 with an accessible web interface where the basic.config page contains an editable PSK field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding on the pre-shared key field to neutralize XSS payloads; validate and sanitize all user-supplied data before rendering. Check vendor for firmware updates.

Fix this in Tew 831dr Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30326 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30326 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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