dbcve.org
Vigor2925 FirmwareOperating system · Draytek

CVE-2019-16534

MEDIUM · 6.1 CVSS v3.1 Published 2019-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
On DrayTek Vigor2925 devices with firmware 3.8.4.3, XSS exists via a crafted WAN name on the General Setup screen. NOTE: this is an end-of-life product.

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 confidence

A stored XSS vulnerability exists in the WAN name field on the General Setup screen of DrayTek Vigor2925 routers running firmware 3.8.4.3. An authenticated attacker can inject malicious JavaScript code into the WAN name parameter, which executes when other users view the affected page.

MitigationSince the device is end-of-life with no vendor patch available, implement compensating controls such as restricting web management interface access to trusted IP addresses via VPN or ACLs, or replace the device with a supported model.

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
Vigor2925 FirmwareOperating system
Affected:= 3.8.4.3

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the router model
    Check the device label, web interface status page, or administrative console to confirm the device is a DrayTek Vigor2925 series router.
    Affected if The device is not a DrayTek Vigor2925, then this specific CVE does not apply.
  2. Check the firmware version
    Log into the router web interface and navigate to System Maintenance > Firmware Upgrade or Status page to identify the installed firmware version.
    Affected if The firmware version is 3.8.4.3, matching the affected version. If the version differs, this specific CVE may not apply.
  3. Verify web management interface accessibility
    Check if the router web interface (HTTP/HTTPS on ports 80/443 or custom port) is reachable from untrusted network segments. Review firewall rules, port forwarding, or WAN access settings.
    Affected if The web interface is accessible from untrusted networks without VPN or IP restrictions, allowing potential authenticated attackers to reach the vulnerable page.
  4. Inspect the WAN name configuration
    Navigate to WAN > General Setup in the router web interface. Examine the WAN name fields for each WAN interface and check the HTML source or application logs for any injected script tags.
    Affected if The WAN name field contains unsanitized script content (such as <script> tags or JavaScript event handlers) indicating exploitation has occurred.
  5. Review user session access
    Determine if untrusted or guest users have administrative credentials or can obtain authenticated access to the router web interface.
    Affected if Untrusted users have administrative access to the router, enabling them to inject the stored XSS payload into the WAN name field.

You are affected if you are running a DrayTek Vigor2925 with firmware version 3.8.4.3 and the router web management interface is accessible to untrusted users who can access the General Setup screen to inject or have already injected malicious scripts into the WAN name 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

Since the device is end-of-life with no vendor patch available, implement compensating controls such as restricting web management interface access to trusted IP addresses via VPN or ACLs, or replace the device with a supported model.

Fix this in Vigor2925 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-16534 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2019-16534 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