dbcve.org
Wmr 300 FirmwareOperating system · Buffalotech

CVE-2016-1135

MEDIUM · 6.1 CVSS v3.0 Published 2016-01-22
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
Cross-site scripting (XSS) vulnerability on BUFFALO BHR-4GRV2 devices with firmware 1.04 and earlier, WEX-300 devices with firmware 1.90 and earlier, WHR-1166DHP devices with firmware 1.90 and earlier, WHR-300HP2 devices with firmware 1.90 and earlier, WHR-600D devices with firmware 1.90 and earlier, WMR-300 devices with firmware 1.90 and earlier, WMR-433 devices with firmware 1.01 and earlier, and WSR-1166DHP devices with firmware 1.01 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

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

Multiple BUFFALO wireless router models (BHR-4GRV2, WEX-300, WHR-1166DHP, WHR-300HP2, WHR-600D, WMR-300, WMR-433, WSR-1166DHP) contain a reflected XSS vulnerability in their web management interfaces. The vulnerability allows unauthenticated remote attackers to inject arbitrary HTML or JavaScript through unspecified vectors in the firmware web server.

MitigationUpdate firmware to versions newer than those listed (BHR-4GRV2: >1.04, WEX-300/WHR-1166DHP/WHR-300HP2/WHR-600D/WMR-300: >1.90, WMR-433/WSR-1166DHP: >1.01). If updates unavailable, restrict administrative interface access to trusted networks only.

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
Wmr 300 FirmwareOperating system
Affected:= 1.90
Wex 300 FirmwareOperating system
Affected:= 1.90
Wmr 433 FirmwareOperating system
Affected:= 1.01
Bhr 4grv2 FirmwareOperating system
Affected:= 1.04
Whr 300hp2 FirmwareOperating system
Affected:= 1.90
Whr 1166dhp FirmwareOperating system
Affected:= 1.90
Whr 600d FirmwareOperating system
Affected:= 1.90
Wsr 1166dhp FirmwareOperating system
Affected:= 1.01

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.0/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 BUFFALO router model
    Locate the model number on the device label (often on the bottom or back of the router) or log into the web management interface and check the status or system information page for the exact model designation
    Affected if The model is one of: BHR-4GRV2, WEX-300, WHR-1166DHP, WHR-300HP2, WHR-600D, WMR-300, WMR-433, or WSR-1166DHP
  2. Determine the installed firmware version
    In the router web management interface, navigate to the Status or System Information page and locate the firmware version field. Alternatively, check the version information in the administration or settings section
    Affected if The firmware version matches exactly: 1.90 (WMR-300, WEX-300, WHR-1166DHP, WHR-300HP2, WHR-600D), 1.01 (WMR-433, WSR-1166DHP), or 1.04 (BHR-4GRV2)
  3. Verify the web management interface is accessible
    Attempt to access the router web interface by entering the router IP address (commonly 192.168.1.1 or 192.168.11.1) in a web browser. Confirm the login page or admin dashboard loads
    Affected if The web management interface is reachable on the network (the XSS vulnerability exists in the web server component)
  4. Confirm the specific firmware version is affected
    Cross-reference your identified model and firmware version against the affected versions: WMR-300/WEX-300/WHR-1166DHP/WHR-300HP2/WHR-600D at version 1.90; WMR-433/WSR-1166DHP at version 1.01; BHR-4GRV2 at version 1.04
    Affected if You are running one of these exact version numbers on an affected model

You are affected if you own one of the eight listed BUFFALO router models and your device is running exactly firmware version 1.90, 1.01, or 1.04 (depending on model), with the web management interface accessible on your network.

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

Update firmware to versions newer than those listed (BHR-4GRV2: >1.04, WEX-300/WHR-1166DHP/WHR-300HP2/WHR-600D/WMR-300: >1.90, WMR-433/WSR-1166DHP: >1.01). If updates unavailable, restrict administrative interface access to trusted networks only.

Fix this in Wmr 300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1135 — 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-2016-1135 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