CVE-2015-5995
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 · uneditedMediabridge Medialink MWN-WAPR300N devices with firmware 5.07.50 and Tenda N3 Wireless N150 devices allow remote attackers to obtain administrative access via a certain admin substring in an HTTP Cookie 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 confidenceAuthentication bypass vulnerability in Mediabridge Medialink MWN-WAPR300N (firmware 5.07.50) and Tenda N3 Wireless N150 routers allows remote attackers to gain administrative privileges by including an 'admin' substring in the HTTP Cookie header, bypassing normal authentication controls.
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 dataall versions<= 5.07.50CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the router label on the device or log into the admin web interface (typically at 192.168.0.1 or 192.168.1.1) and check the device model under Status or System Information pagesAffected if Model is Mediabridge Medialink MWN-WAPR300N or Tenda N3 Wireless N150
-
Check firmware versionIn the router admin web interface, navigate to Status or System Information to view the installed firmware versionAffected if Firmware version is 5.07.50 or lower on Mediabridge Medialink MWN-WAPR300N, or any version on Tenda N3 Wireless N150
-
Test authentication bypass vulnerabilitySend an HTTP request to the router login page with a Cookie header containing the substring 'admin' (for example: Cookie: admin=1 or Cookie: username=admin). Observe if the request is granted administrative access without valid credentialsAffected if The router grants administrative access when the Cookie header contains 'admin' substring, bypassing normal authentication
Your environment is affected if you operate a Mediabridge Medialink MWN-WAPR300N router with firmware 5.07.50 or lower, or any Tenda N3 Wireless N150 router, and the cookie-based authentication bypass test succeeds.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate router firmware if a patch is available; otherwise replace affected devices with currently supported models, as these legacy consumer routers are likely end-of-life with no security updates.
Latest firmware version available from Medialink or Tenda support website (specific version numbers not disclosed in vulnerability note)
- 1. Identify the exact model number of the affected device (Medialink MWN-WAPR300N or Tenda N3 Wireless N150)
- 2. Visit the manufacturer's official support website to check for available firmware updates
- 3. Download the latest firmware version available for your specific model
- 4. Consult the device's user manual for firmware update instructions, typically involving accessing the web administration interface
- 5. Backup current device configuration before applying the firmware update
- 6. Apply the firmware update following manufacturer instructions
- 7. After updating, verify the vulnerability is resolved by attempting the Cookie-based authentication bypass
- 8. If no firmware update is available from the manufacturer, consider replacing the device with a newer model that receives active security support
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5995 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5995 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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