dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-5842

HIGH · 7.3 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A security vulnerability has been detected in decolua 9router up to 0.3.47. The impacted element is an unknown function of the file /api of the component Administrative API Endpoint. The manipulation leads to authorization bypass. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 0.3.75 is sufficient to resolve this issue. It is suggested to upgrade the affected component.

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

An authorization bypass vulnerability exists in the /api administrative endpoint of decolua 9router versions up to 0.3.47. This allows remote attackers to bypass authentication controls and access administrative functions without proper authorization. The vulnerability has been publicly exploited.

MitigationUpgrade decolua 9router to version 0.3.75 or later to remediate the authorization bypass. Verify that administrative API endpoints properly enforce authentication after upgrading.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 decolua 9router installation
    Locate the decolua 9router installation and determine its version number, typically via software inventory, package manager, or firmware version display
    Affected if The installed version is 0.3.47 or any version up to 0.3.47
  2. Verify API endpoint exposure
    Check if the /api administrative endpoint is exposed and reachable on the network, typically via web browser or curl request to the endpoint
    Affected if The /api endpoint is accessible from the network without any authentication prompt
  3. Test authentication bypass
    Send an unauthenticated request to the /api endpoint (for example, GET /api/admin/status or similar administrative function) and observe if the server returns administrative data or accepts administrative commands
    Affected if The /api endpoint returns administrative data or executes administrative commands without requiring valid authentication credentials
  4. Review authentication configuration
    Inspect the decolua 9router configuration files or administrative settings to verify whether authentication is explicitly required and enforced for the /api endpoint
    Affected if Authentication for the /api endpoint is disabled, misconfigured, or set to an ineffective enforcement level

A user is affected if decolua 9router version 0.3.47 or earlier is installed and the /api administrative endpoint can be accessed or manipulated without proper 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 decolua 9router to version 0.3.75 or later to remediate the authorization bypass. Verify that administrative API endpoints properly enforce authentication after upgrading.

Recommended fix Moderate confidence

0.3.75

  1. 1. Back up the current decolua 9router installation and configuration
  2. 2. Obtain version 0.3.75 of decolua 9router from the official source
  3. 3. Stop the decolua 9router service
  4. 4. Replace the existing decolua 9router files with the new version 0.3.75
  5. 5. Restore any custom configurations from the backup if needed
  6. 6. Restart the decolua 9router service
  7. 7. Verify the version has been updated to 0.3.75 or later
  8. 8. Test that the /api administrative endpoint now properly enforces authorization

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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