dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 Jun 2025.
Vigor300b FirmwareOperating system · Draytek

CVE-2024-12987

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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, which was classified as critical, was found in DrayTek Vigor2960 and Vigor300B 1.5.1.4. Affected is an unknown function of the file /cgi-bin/mainfunction.cgi/apmcfgupload of the component Web Management Interface. The manipulation of the argument session leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.5.1.5 is able to address this issue. It is recommended 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

OS command injection vulnerability in DrayTek Vigor2960 and Vigor300B routers allows remote attackers to execute arbitrary commands via the 'session' parameter in the /cgi-bin/mainfunction.cgi/apmcfgupload endpoint of the Web Management Interface. The flaw is exploitable remotely without authentication due to insufficient input sanitization.

MitigationUpgrade DrayTek firmware to version 1.5.1.5 or later to remediate this critical command injection vulnerability. If immediate upgrade is not possible, restrict access to the web management interface to trusted IP addresses only.

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
Vigor300b FirmwareOperating system
Affected:= 1.5.1.4
Vigor2960 FirmwareOperating system
Affected:= 1.5.1.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 router model
    Access the router's web management interface or check the device label to confirm it is a Draytek Vigor2960 or Vigor300B
    Affected if Device is not one of these two models
  2. Check firmware version
    Log into the web interface and navigate to System Maintenance > Firmware Upgrade or check the version displayed in the status/dashboard area
    Affected if Firmware version is exactly 1.5.1.4
  3. Confirm web management interface is accessible
    Verify the router's web interface is reachable via HTTP or HTTPS on the configured IP address
    Affected if Web interface is exposed and accessible
  4. Verify vulnerable endpoint exists
    Attempt to access the URL path /cgi-bin/mainfunction.cgi/apmcfgupload on the router
    Affected if Endpoint responds with any status (200, 400, etc.) indicating it exists

Device is affected if it is a Draytek Vigor2960 or Vigor300B running firmware version 1.5.1.4 with the web management interface 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade DrayTek firmware to version 1.5.1.5 or later to remediate this critical command injection vulnerability. If immediate upgrade is not possible, restrict access to the web management interface to trusted IP addresses only.

Recommended fix High confidence

1.5.1.5

  1. Download the firmware version 1.5.1.5 for your device (Vigor300b or Vigor2960) from the official DrayTek support website (fw.draytek.com.tw or draytek.com)
  2. Access the web management interface of the affected DrayTek device
  3. Navigate to the System Maintenance or Firmware Upgrade section
  4. Upload and apply the version 1.5.1.5 firmware file
  5. Verify the upgrade was successful by checking the firmware version in the web interface or system status

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

Fix this in Vigor300b Firmware Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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