dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-6274

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
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
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
Improper Authentication, Missing authentication for critical function, Weak Authentication vulnerability in DTS Electronics Industry and Trade Ltd. Co. Redline WR3200 allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Redline WR3200: from 7.1.3 before 7.1.8.

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

Authentication bypass vulnerability in Redline WR3200 routers (versions 7.1.3-7.1.7) allows unauthorized access to critical functions that should be protected by Access Control Lists due to missing or weak authentication mechanisms.

MitigationUpgrade Redline WR3200 firmware to version 7.1.8 or later to remediate the authentication bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Identify device model
    Access the router's web administration interface or check the device label/menu to confirm the model is Redline WR3200
    Affected if The device is a Redline WR3200 router
  2. Determine firmware version
    Log into the router admin panel and navigate to System, Status, or About section to view the current firmware version number
    Affected if The installed firmware version falls within 7.1.3 through 7.1.7 inclusive
  3. Verify authentication on critical functions
    Attempt to access restricted administrative functions, APIs, or endpoints without providing credentials to test if authentication is enforced
    Affected if Unauthenticated access to restricted functionality is granted, indicating ACL bypass is present
  4. Check for unauthorized access to management features
    Use a browser or HTTP tool to reach critical management pages (such as network settings, user management, or system configuration) without logging in
    Affected if These pages load without requiring authentication credentials

You are affected if the device is a Redline WR3200 running firmware version 7.1.3, 7.1.4, 7.1.5, 7.1.6, or 7.1.7 and critical functions are accessible without authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Redline WR3200 firmware to version 7.1.8 or later to remediate the authentication bypass vulnerability.

Recommended fix High confidence

7.1.8

  1. 1. Identify the current firmware version of the Redline WR3200 device by accessing the administrative web interface or checking via CLI
  2. 2. If the current version is between 7.1.3 and 7.1.7 (inclusive), the device is vulnerable and requires an upgrade
  3. 3. Download the firmware version 7.1.8 or later from the official vendor (DTS Electronics Industry and Trade Ltd. Co.)
  4. 4. Access the device administration panel and navigate to the firmware upgrade section
  5. 5. Upload the firmware file and initiate the upgrade process
  6. 6. Wait for the device to reboot and verify the new firmware version is 7.1.8 or later
  7. 7. After upgrade, verify the authentication mechanisms are functioning properly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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