Ns Wir150ne FirmwareOperating system · Nisuta

CVE-2013-7282

HIGH · 10.0 CVSS v2.0 Published 2014-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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
The management web interface on the Nisuta NS-WIR150NE router with firmware 5.07.41 and Nisuta NS-WIR300N router with firmware 5.07.36_NIS01 allows remote attackers to bypass authentication via a "Cookie: :language=en" HTTP header.

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

The management web interface on Nisuta NS-WIR150NE and NS-WIR300N routers contains an authentication bypass vulnerability where adding a 'Cookie: :language=en' HTTP header allows attackers to access the admin interface without valid credentials. This is a direct authentication bypass requiring only a crafted HTTP header.

MitigationRestrict network access to the router's management interface using firewall rules to block external HTTP/HTTPS access, or disable remote management entirely if not required. If firmware updates are available from the vendor, apply them immediately.

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
Ns Wir150ne FirmwareOperating system
Affected:= 5.07.41
Ns Wir150neHardware / appliance
Affected:all versions
Ns Wir300n FirmwareOperating system
Affected:= 5.07.36_nis01
Ns Wir300nHardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 router model
    Access the router's web interface or check the device label to confirm the model is NS-WIR150NE or NS-WIR300N
    Affected if Model is Nisuta NS-WIR150NE or NS-WIR300N
  2. Check firmware version
    Log into the router admin interface and navigate to the status or firmware information page to find the installed firmware version
    Affected if Firmware version is 5.07.41 (NS-WIR150NE), 5.07.36_nis01 (NS-WIR300N), or any version for either model since all versions are affected
  3. Test authentication bypass vulnerability
    Send an HTTP GET request to the router's web interface (typically 192.168.1.1 or 192.168.0.1) with the header 'Cookie: :language=en' and attempt to access an admin page without providing credentials
    Affected if The response grants access to admin functionality or returns admin pages without requiring login credentials
  4. Verify remote management is accessible
    Confirm the router's web interface is reachable from the network segment you are testing from (not just localhost)
    Affected if The management interface is reachable over the network

You are affected if you own a Nisuta NS-WIR150NE or NS-WIR300N router with any firmware version and the crafted Cookie header grants unauthenticated admin access.

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

Restrict network access to the router's management interface using firewall rules to block external HTTP/HTTPS access, or disable remote management entirely if not required. If firmware updates are available from the vendor, apply them immediately.

Fix this in Ns Wir150ne Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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