dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-5437

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 vulnerability classified as critical has been found in Multilaser Sirius RE016 MLT1.0. Affected is an unknown function of the file /cgi-bin/cstecgi.cgi of the component Password Change Handler. The manipulation leads to improper authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

The Multilaser Sirius RE016 router (firmware MLT1.0) contains an authentication bypass vulnerability in its web interface CGI script (/cgi-bin/cstecgi.cgi) specifically within the Password Change Handler. An unauthenticated remote attacker can manipulate the password change functionality to gain unauthorized access to the device administration interface, bypassing proper authentication controls.

MitigationSince the vendor has not responded to disclosure, implement network-based controls: restrict access to the router's admin interface using firewall rules or VLAN segmentation to limit exposure to trusted networks only. Consider replacing the device if a firmware update is unavailable.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 device model
    Access the router admin interface or check device labeling to confirm the model is Multilaser Sirius RE016. You can also often find this via the web interface login page title or footer, or by checking DHCP/DNS device names on your network.
    Affected if The device is a Multilaser Sirius RE016 router.
  2. Check firmware version
    Log into the router web interface and navigate to the Status or System Information page to view the installed firmware version. Look for 'MLT1.0' as the firmware version.
    Affected if The firmware version is MLT1.0.
  3. Verify CGI script accessibility
    Attempt to access the path /cgi-bin/cstecgi.cgi on the router's IP address using a web browser or curl command (e.g., curl http://<router-ip>/cgi-bin/cstecgi.cgi). A valid response indicates the script is exposed.
    Affected if The /cgi-bin/cstecgi.cgi endpoint returns a valid HTTP response without authentication.
  4. Assess network exposure
    Determine if the router's admin web interface (typically ports 80 or 443) is accessible from untrusted networks. Check firewall rules, port forwarding configurations, and WAN-facing exposure.
    Affected if The router admin interface is accessible from outside the trusted local network.
  5. Review admin account changes
    Log into the router admin interface and verify that the administrator account credentials have not been changed without your knowledge. Check for any unauthorized user accounts.
    Affected if The administrator password was changed unexpectedly or unauthorized admin accounts exist.

You are affected if you are running a Multilaser Sirius RE016 router with firmware MLT1.0 and the web interface /cgi-bin/cstecgi.cgi is accessible to untrusted networks, allowing potential unauthenticated password manipulation.

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

Since the vendor has not responded to disclosure, implement network-based controls: restrict access to the router's admin interface using firewall rules or VLAN segmentation to limit exposure to trusted networks only. Consider replacing the device if a firmware update is unavailable.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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