dbcve.org
Vigor3900 FirmwareOperating system · Draytek

CVE-2024-45882

HIGH · 8.0 CVSS v3.1 Published 2024-11-04
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
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
DrayTek Vigor3900 1.5.1.3 contains a command injection vulnerability. This vulnerability occurs when the `action` parameter in `cgi-bin/mainfunction.cgi` is set to `delete_map_profile.`

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

Command injection vulnerability in DrayTek Vigor3900 router firmware version 1.5.1.3 allows remote attackers to execute arbitrary OS commands via the cgi-bin/mainfunction.cgi endpoint when the action parameter is set to delete_map_profile, without proper input sanitization.

MitigationIsolate affected devices from untrusted networks, restrict access to the management interface to authorized IPs only, and apply vendor firmware patch when released; consider disabling remote management if not required.

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
Vigor3900 FirmwareOperating system
Affected:= 1.5.1.3

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

CVSS:3.1/AV:A/AC:L/PR:L/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. Confirm device is DrayTek Vigor3900
    Access the router administration interface or check the device model number via the web UI, command line, or physical label
    Affected if Device model is not Vigor3900
  2. Check firmware version is 1.5.1.3
    In the router web interface, navigate to System Maintenance > Firmware Upgrade or similar section to view the current firmware version. Alternatively, check via CLI if available.
    Affected if Firmware version equals 1.5.1.3 exactly
  3. Verify cgi-bin/mainfunction.cgi endpoint is accessible
    Attempt to access the URI /cgi-bin/mainfunction.cgi on the router's management interface. This is typically accessible on ports 80 or 443.
    Affected if Endpoint responds to requests without authentication restrictions
  4. Confirm delete_map_profile action is available
    Send a request to mainfunction.cgi with action=delete_map_profile parameter. The vulnerability exists when this specific action parameter is processed.
    Affected if The delete_map_profile action is recognized and processed by the application

The environment is affected only if the device is a DrayTek Vigor3900 running firmware version exactly 1.5.1.3 and the management interface with the cgi-bin/mainfunction.cgi endpoint is accessible.

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

Isolate affected devices from untrusted networks, restrict access to the management interface to authorized IPs only, and apply vendor firmware patch when released; consider disabling remote management if not required.

Fix this in Vigor3900 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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