dbcve.org
Mzk Mf300n FirmwareOperating system · Planex

CVE-2024-30219

MEDIUM · 6.8 CVSS v3.1 Published 2024-04-15
Fix available
A fix is available. Upgrade to after 1.18 or later.
See remediation →
70/100
Remediation priority · Elevated
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
Active debug code vulnerability exists in PLANEX COMMUNICATIONS wireless LAN routers. If a logged-in user who knows how to use the debug function accesses the device's management page, an unintended operation may be performed. Note that MZK-MF300N is no longer supported, therefore the update for this product is not provided.

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

A debug function remains accessible in production firmware of PLANEX wireless LAN routers. An authenticated user with knowledge of the debug function can perform unintended operations through the device's web management interface. Since this affects EOL hardware with no patch available, the vulnerability stems from debug code that should have been removed before deployment.

MitigationAs no firmware update will be provided, organizations should replace affected devices with supported hardware. If immediate replacement is not feasible, restrict administrative access to trusted personnel only and implement network segmentation to limit exposure.

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 data
Mzk Mf300n FirmwareOperating system
Affected:all versions
Mzk Mf300hp2 FirmwareOperating system
Affected:<= 1.18

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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 the exact PLANEX router model
    Check the device product label on the bottom of the router or the web management interface system status page to confirm the exact model number (Mzk Mf300n or Mzk Mf300hp2).
    Affected if The device is a Planex Mzk Mf300n (all versions) or Mzk Mf300hp2 with firmware version 1.18 or lower.
  2. Determine the firmware version on Mzk Mf300hp2
    Log into the web management interface and navigate to the Firmware Upgrade or System Information page to view the installed firmware version number.
    Affected if The firmware version is 1.18 or lower on the Mzk Mf300hp2 model.
  3. Check for debug or diagnostic pages in the web interface
    Look for unusual or hidden menu items in the router web interface such as 'debug', 'diag', 'test', 'factory', 'console', or similar diagnostic sections not typically found in consumer router interfaces.
    Affected if Any debug, diagnostic, or test pages are visible or accessible in the web management interface.
  4. Probe for hidden debug endpoints
    Using a web browser or HTTP tool, attempt to access common debug paths on the router such as /debug.htm, /diag.html, /test.cgi, /factory.asp, or /console.shtml (adjust based on the router's actual web server technology).
    Affected if These debug endpoints return a valid response rather than a 404 error.
  5. Inspect web interface source code for debug functions
    View the HTML source code of the router's main administration page and search for commented-out code, hidden forms, or functions named debug, test, factory_reset, or similar that may indicate leftover debug functionality.
    Affected if Debug-related functions, hidden parameters, or commented debug code are present in the web interface files.

You are affected if you own a Planex Mzk Mf300n (any firmware version) or a Mzk Mf300hp2 with firmware version 1.18 or lower, and any debug functionality or diagnostic pages are accessible in the web management interface.

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
Upgrade available Upgrade to a release after 1.18
Interim mitigation

As no firmware update will be provided, organizations should replace affected devices with supported hardware. If immediate replacement is not feasible, restrict administrative access to trusted personnel only and implement network segmentation to limit exposure.

Fix this in Mzk Mf300n Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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