dbcve.org
CWE-290Weakness · CWE-290

CVE-2025-36754

CRITICAL · 9.3 CVSS v4.0 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 authentication mechanism on web interface is not properly implemented. It is possible to bypass authentication checks by crafting a post request with new settings since there is no session token or authentication in place. This would allow an attacker for instance to point the device to an arbitrary address for domain name resolution to e.g. facililitate a man-in-the-middle (MitM) attack.

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 web interface lacks proper authentication enforcement, allowing unauthenticated attackers to send POST requests that modify device settings including DNS configuration, enabling man-in-the-middle attacks.

MitigationImplement proper authentication, session management, and CSRF protection for all web interface endpoints, especially those handling device configuration changes.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 web interface exposure
    Determine if the device web management interface is accessible from the network. Check for open ports 80, 443, or custom web service ports using 'netstat -an | grep LISTEN' or a port scanner.
    Affected if The web interface is externally accessible or on an internal network with insufficient access controls.
  2. Test authentication on configuration endpoints
    Send a crafted unauthenticated POST request to common configuration endpoints such as /dns, /network/dns, /settings, or /config using curl or Burp Suite. Include DNS server parameters in the request body.
    Affected if The device accepts and processes the POST request without requiring authentication (HTTP 200 or successful configuration change response).
  3. Verify DNS configuration modification
    Check current DNS settings via the web interface or CLI command such as 'cat /etc/resolv.conf' or 'show dns configuration' before and after sending an unauthenticated POST request.
    Affected if DNS settings can be changed without any authentication token, session cookie, or login credentials.
  4. Inspect HTTP response headers and status codes
    Make unauthenticated GET requests to web interface pages and examine response headers for authentication-related cookies, tokens, or security headers. Compare to POST attempts.
    Affected if POST requests to configuration endpoints return success (200 OK) without requiring authentication cookies or tokens that were obtained via login.
  5. Review web server authentication configuration
    Examine the web server or application configuration files for authentication enforcement rules. Look for .htaccess, nginx/Apache config, or application-level auth checks on POST handlers.
    Affected if Configuration endpoints lack authentication enforcement rules or permit unrestricted access to POST methods.

If the device web interface accepts unauthenticated POST requests to modify DNS or other device settings, the environment is affected by this authentication bypass vulnerability.

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

Implement proper authentication, session management, and CSRF protection for all web interface endpoints, especially those handling device configuration changes.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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