CVE-2024-51300
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 · uneditedIn Draytek Vigor3900 1.5.1.3, attackers can inject malicious commands into mainfunction.cgi and execute arbitrary commands by calling the get_rrd function.
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 confidenceCommand injection vulnerability in Draytek Vigor3900 version 1.5.1.3 allows attackers to inject and execute arbitrary commands through the get_rrd function in mainfunction.cgi. The flaw enables full compromise of the network device with high severity (CVSS 8.8).
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= 1.5.1.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web management interface or check the device label. Confirm it is a Draytek Vigor3900 router.Affected if The device is not a Draytek Vigor3900, then it is not affected by this specific CVE.
-
Check the firmware versionLog into the web interface and navigate to System Maintenance > Firmware Upgrade, or use the CLI command 'sys firmver' to retrieve the installed firmware version.Affected if The firmware version is exactly 1.5.1.3, then the device is affected. If the version differs (higher or lower), it may not be affected by this specific vulnerability.
-
Verify the vulnerable CGI endpoint existsCheck if mainfunction.cgi is accessible on the device by attempting to access the URL path /cgi-bin/mainfunction.cgi or reviewing the device's web root directory structure if you have filesystem access.Affected if The mainfunction.cgi file exists and contains a get_rrd function handler, then the vulnerable code path is present on the device.
-
Assess web interface exposureDetermine if the device's web management interface (port 80/443) is reachable from untrusted networks by reviewing firewall rules, NAT configurations, or network access lists.Affected if The web interface is exposed to untrusted networks without proper access controls, the vulnerability is remotely exploitable.
A user is affected if they are running Draytek Vigor3900 firmware version exactly 1.5.1.3 with the web management interface accessible, as this specific version contains the command injection flaw in mainfunction.cgi's get_rrd function.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch or firmware update for Draytek Vigor3900 to the latest available version. If no patch is available, restrict access to the device's management interface using network segmentation or firewall rules.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51300 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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